RE: non-x86 development
martin.stachon at worldonline.cz wrote:
> AppleScript is based on its syntax.), but I think the API
> for MacOS <=9 is different than for MacOS X.
> So you will have to write two versions of Eu for Mac.
Just whip up a PPC UNIX version of Eu for that. Doesn't have to be Mac
specific since MacOS X is just BSD UNIX
> It is possible to create programs with dual code (FAT) - 68k and
> PowerPC.
> (With two CODE resources)
actually, there's the standard CODE resource for 68k programs, and then
PowerPC code is contained in the data fork. that's why you get an error
running a PPC program with no 68k code(no CODE resource)
> What about some built-in routines - getenv, command_line.
> Eu for Mac would be isolated from other Eu world,
> because you could run only some generic command-line apps,
> (I don't know how would be emulated passing parameters via command
> line?)
ah, you're forgetting MacOS X's UNIX-side. you can simply open a
terminal and call Eu like "exu hello", of course it'd be kind of
pointless because it wouldn't be Mac-specific, just PPC UNIX-specific.
> I would help you too (I have a 68000, 68030 and PowerPC 603 machine)
PPC 603? i made a mistake and got a Centris 610. doesn't even have an
FPU :)
|
Not Categorized, Please Help
|
|
