1. RE: non-x86 development
you really know your stuff :) anyway, i'm /sorta/ biased toward the 68k,
since i've never seen much PowerPC stuff. but when i said "non-x86
development", i wasn't just talking about 68k stuff. there's also
PowerPC, SPARC, etc. I suppose the assembly part is why robert didn't
port it to other architectures, but with a small handful of non-x86
programmers, i suppose robert could just pick some assembly files when
he was compiling Eu for some architecture, or another set for another
architecture
martin.stachon at worldonline.cz wrote:
> I looked at few pieces of code, and MacOS API seems more complicated to
> me than WIN32 API.
i hear ya, brother
> ':' instead of '\\', but creating GUI apps would be dfficult.
yeah, especially since the Mac OS seems less centered around shared
libraries than other OSes
2. RE: non-x86 development
David Cuny wrote:
I wouldn't make that assumption until seeing Robert's source. You could
be
> right, but at this point, it's all speculation. When I get my copy, I
> hope
> to give it a whirl on an emulated 68K Mac.
when you decide to emulate a mac, just ask if you need anything. i've
got a coupla large disk images(system software, downloads, MPW for
programming, etc...), though i think i may have oversized the second
one, but bzip2 should be able to handle it considering it's mostly empty
3. RE: non-x86 development
vMac?? ugh...
David Cuny wrote:
> I've used the vMac images with good success. Is you've got MPW, you
> should
4. 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 :)
5. RE: non-x86 development
sephiroth _ wrote:
> 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-
Isn't there a MS WINDOWS emulator for the MAC so you could use EXW?
I think that pete eberlein had a euphoria clone running on
BEE maybe when the source is available you could look at pete's
source and use it as a guide to write a port.
Bernie
6. RE: non-x86 development
i suppose it would work, but then it wouldn't be a real mac port
> Isn't there a MS WINDOWS emulator for the MAC so you could use EXW?
> I think that pete eberlein had a euphoria clone running on
> BEE maybe when the source is available you could look at pete's
> source and use it as a guide to write a port.
i think a few of us here on the list(at the moment, me, david cuny, and
one other) have pete's source
7. RE: non-x86 development
martin.stachon at worldonline.cz wrote:
> It is a long a time since I have been 'hacking' programs with ResEdit,
> but
> under Mac there is no code in data fork. Most programs have data fork
> empty.
> (The resource fork is a great thing. All program data is contained in
> program, sorted by type, and easy editable)
> I suppose there is small 68k code which decides if run 68k or PPC
> version
> CODE.
i've tested this myself. i built a program with no 68k code and it had
no code resource. all PPC code is stored in the data fork. 68k Mac OSes
just ignore the data fork when loading a program. that's why you get
error -92(resource not found) when running a PowerPC-only binary on an
older Mac OS
> It s possible to upgrade some 68k machines to PPC.
i'd get one of those fancy upgrade cards, but they're so damned
expensive($249)!
