Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!bu.edu!xylogics!samsung!uunet!tellab5!toth
From: toth@tellabs.com (Joseph G. Toth Jr.)
Newsgroups: comp.sys.apple2
Subject: Re: C compilers
Summary: HyperC Linker ??
Message-ID: <5017@tellab5.tellabs.com>
Date: 10 Jan 91 13:53:03 GMT
References: <363@generic.UUCP>
Sender: news@Tellabs.COM
Lines: 29

In article <363@generic.UUCP>, ericmcg@pnet91.cts.com (Eric Mcgillicuddy) writes:
[Aztec C stuff deleted]
> Basically, you are stuck with HyperC. You might consider rewriting the Linker
> (no I don't have source for the linker), I have no idea how difficult this
> would be, but there are likely a number of people that would be interested.

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.

Joe Toth
Tellabs, Inc.
Lisle, Il.

--
------------------------------------------------+---------------------
Maybe I shouldn't have done it, sarcasm is so   | Joseph G. Toth Jr.
seldom understood.  Don't FLAME on me, please.  | uunet!tellab5!toth