Re: Mike and Ward, what next?

Stephen Pelc wrote:
> When ****ting VFX Forth to another platform, changing CPU is
> the least of the problems. The real work is in the binary
> format, e.g. ELF, and in the operating system API interface.
>
> I have not looked at source code for the Mac Forths, so I can't
> comment on their ****ting issues, but providing that only the CPU
> changes, the Forth kernel was designed for ****tability, and the
> existing O/S kernel interfaces do not change, the job is quite
> straight forward. Whether the authors have the energy for it
> is another matter.

You'd have to dig up some info on the Mach-O file format.  I found some
general overview information on Apple's website, but I don't think they
provide any API to create them aside from compilers like XCode and so
forth.  So it would have to be by hand, so to speak.

As for the OS itself, the Objective C runtime sup****ts bridging with
other languages so that ObjC cl***** (in this case Cocoa) can be
manipulated from outside.  The API is C-based, so I don't know what
kind of effort it is to hook it up via assembly (which is what I assume
you would try to do).  

Erik