2 ms·
>It was originally just meant to handle localizable resources Not quite. An application's executable code was also stored in the resource fork, as CODE resourc
by Kristine1975 10y ago
>It was originally just meant to handle localizable resources
Not quite. An application's executable code was also stored in the resource fork, as CODE resources (one or several, so parts of the code could be loaded and unloaded as needed; initially there was also a size limit of 64k per CODE resource).
When Apple switched to PPC, the PPC code was stored in the data fork and the 68k code in CODE resources.
- kalleboo 10y agoI meant originally as in when the Mac was still in development - I remembered it from here http://www.folklore.org/StoryView.py?story=The_Grand_Unified_Model.txt http://www.folklore.org/StoryView.py?story=The_Grand_Unified... I may have unconsciously filled in some blanks in my memory that weren't actually there - the story mentions Andy Hertzfeld used the Resource Manager to manage the swapping in and out of code segments and I think I read it as a hack to use the Resource Manager in a way it wasn't intended, but it may very well have been intended that way to begin with.