If planning to support arbitrary *new* m68k software calling arbitrary *new* AROS code, this might be an issue, but what would be the point of supporting that? If only supporting m68k software interacting only with AROS versions of software available for 3.1, then the set of possible software is for all intents and purposes pretty much finite and unchanging and it's just a matter of how adding mappings as/when problems are found with specific applications.
Exactly the point! Emumiga is intended for old binary-only stuff. New applications are hopefully open sourced and/or running natively on x86 AROS.
Emumiga relies totally on that AROS is implementing AmigaOS3.1 close enough. So, if AROS moves in a direction where it is forced to abandon some of the old APIs I'm basically screwed. I think that is the biggest risk in the long run.
I won't speculate about whether or not current Emumiga does it the right way, as I haven't read the code, but this is by no means an unsolvable problem.
A believer! Thank you. :-)
