Linked by Thom Holwerda on Tue 18th Jul 2006 22:51 UTC, submitted by Raffaele
"In a previous item, we described how the AmigaOS4.0 memory system works in terms of managing memory allocations from the top. However, there is more to allocating memory than that. The object caches of course work on memory that has already been mapped into the virtual memory space. But both the virtual address ranges, as well as the physical memory has to come from a source, too."
Thread beginning with comment 144574
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:
2006-07-18
One more thing which is very interessting for OS4, is the availability of the development tools. True is, that one needs to get an AmigaOS4 SDK to get access to all structures and header files and documentation etc.
But the SDK includes and up to date gcc (version 4) and other tools out of the gnu tool chain. Further more, these tools are not only available for the target AmigaOS, but also in form of cross tools. The supported host platforms are Win(XP)/cygwin, MacOSX, Linux (ppc and x86) and Sun's OS (AFAIK).
It is e.g. easy to integrate them into Eclipse (up to 3.2, which supports managed make thru the AmigaDT/CDT plugin) on every platform Eclipse runs on.
It might require a machine to test the code, but it does not require one to write it.
Edited 2006-07-19 18:43