Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod!rpi!bu.edu!m2c!wpi.WPI.EDU!greyelf
From: greyelf@wpi.WPI.EDU (Michael J Pender)
Newsgroups: comp.sys.apple2
Subject: Re: C compilers
Message-ID: <1991Jan14.225521.2133@wpi.WPI.EDU>
Date: 14 Jan 91 22:55:21 GMT
References: <363@generic.UUCP> <5017@tellab5.tellabs.com>
Organization: Worcester Polytechnic Institute
Lines: 30

In article <5017@tellab5.tellabs.com> toth@tellabs.com (Joseph G. Toth Jr.) writes:
>Re-write the Linker??? Why in the world would anybody want (or need) to do
>that?? It has worked just fine for for every compile i have performed.
>
>There do seem to be some problems with the mac codes that convert P-code
>to 6505 (65c02 ??) assembler..
>
>This seems to be the area where Mr. Michael Pender was having problems when
>using floating point operations.  I tried the examples he posted, and they
>bombed horribly when compiled to native code, but executed perfectly when
>I compiled to P-code.
>
>I guess this could still be a linker problem, but I have too many other pieces
>of code, compiled to native code, that work just fine (no linker problems).
>The only difference is that none of them use the floating point operations.

Why don't people tell ME these things :^)  I'll have to try that.

Actually to create a native code object file, compile to native code
and use the -a, -s and -h directive to make addresses absolute, 
I forgot what s is for and -h removes the header.  

The problem then is that display routines in conio are not included with
your program.  Just rename your file shell, and pack the 
files c.system/gs.system opsys and shell on the same disk.

Besides the Pcode is fast enough for most uses.  Its not worth the
extra disk space.

Mike.