Linked by Dmitar Butrovski on Wed 13th Sep 2006 16:04 UTC
Thread beginning with comment 162216
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.





Member since:
2005-07-08
nowdays devs (OS4,AROS,Morphos)just stick to the 3.x API as if it were pure truth, true gold .. this is too bad.
The problem is that the existing applications written for the AmigaOS API expect there to be no memory protection. If you add that, you break compatibility with the old software, and an OS with no software is pretty useless.
Also, I believe AROS is attempting to get AmigaOS 3.X implemented fully before they start changing things. This is the easiest way to get everyone working toward the same goal. They could argue for years about the best way to implement memory protection (or whatever other feature you want added to AROS) but saying "We'll get AmigaOS 3.1 re-implemented first." Is the easiest way to get something done.
no..unfortunatly there's still no memory protection for all flavor of amigaOS systems (this including AROS, Morphos, AmigaOS4, Amithlon..).
I believe (but am not sure) that AmigaOS 4.0 supports limited memory protection. The application has to explicitly ask for it, though. If it was on by default, old code for AmigaOS 3.X would not run without extensive modification.