home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.mac.programmer
- Path: sparky!uunet!paladin.american.edu!darwin.sura.net!mojo.eng.umd.edu!russotto
- From: russotto@eng.umd.edu (Matthew T. Russotto)
- Subject: Re: Sozobon C - a free C for the Mac, too?
- Message-ID: <1992Dec31.223441.15654@eng.umd.edu>
- Date: Thu, 31 Dec 92 22:34:41 GMT
- Organization: Project GLUE, University of Maryland, College Park
- References: <29848@castle.ed.ac.uk>
- Distribution: comp
- Lines: 22
-
- In article <29848@castle.ed.ac.uk> ngse18@castle.ed.ac.uk (J R Evans) writes:
-
- >So given that we can have a basic small compiler running quickly, just how
- >big a job might it be to make this produce Mac code? Comments sought!
- >[e.g. Sozobon doesn't know about the specialised purposes assigned within
- >the Mac to A5, but apart from telling the compiler to leave A5 alone,
- >I guess most of this stuff will appear in the libraries? Is that so? --
- >As is probably obvious, I've done comparitively little Mac
- programming.]
-
- I don't think the compiler itself will be the biggest problem, given
- that you already have a 68000 C compiler for the other platforms.
- there is stuff like treating A5 in a special manner, but comparatively minor
- when you consider your big problem: LINKING. If you want to use the
- Mac libraries, you've got to come up with a working linker, able to
- read MPW .o files or THINK C projects (and the latter isn't
- documented).
- --
- Matthew T. Russotto russotto@eng.umd.edu russotto@wam.umd.edu
- Some news readers expect "Disclaimer:" here.
- Just say NO to police searches and seizures. Make them use force.
- (not responsible for bodily harm resulting from following above advice)
-
