Where the networking stack returns a different range of error numbers based on what OS version you are running under, which range should be returned?
Where the same reason code to a SWI results in different actions, which action prevails?
For ImageFileRenderer, do you think it's best to rework the internals or port the low level sprite changes?
I bet ROL and ROOL haven't come to a collective decision about all of that.
We will still have to see what happens with the existing API incompatibilities. Networking error codes, various WIMP extensions as well as the stuff mentioned above lead developers to cater for both or ignore both. There is also no mention of time scale.
To put my rose tinted spectacles on for a moment, I'll bet that both parties aren't 100% sure themselves how this is going to be done nor how long it will take and how many incompatibilities can be removed before the price/time/benefit ratio becomes too expensive for the small gain it will give.
However an effort like this is appreciated. Anything that aids developers for the platform is bound to be a benefit.
"I use Thunderbird since quite a while now on my Windows machine, but I never discovered any functionality that wasn't covered at least as good as in Pluto"
So the IMAP and SSL functionality in Thunderbird is just as good as Pluto's?
Oh, I forget, Pluto doesn't so IMAP and SSL where as Thunderbird does.
But so does MessengerPro.
"If I gave you a copy of RISC OS 5 for RiscPC today, you'd have deleted it and be back to running 4.02 an hour later"
No /I/ won't. I'll be using to test against a 32-bit only OS.
I don't care that it won't run a ViewFinder, that my 'favorite' desktop utilities (and sillies) won't run.
I'll sit there with a copy of Armalyser and make all those utilities and sillies 32-bit .