Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!mailrus!purdue!tut.cis.ohio-state.edu!ucbvax!pro-generic.cts.COM!ericmcg
From: ericmcg@pro-generic.cts.COM (Eric Mcgillicuddy)
Newsgroups: comp.sys.apple
Subject: Re: Compiler Questions
Message-ID: <7958.infoapple.net@pro-generic>
Date: 27 Nov 89 06:53:38 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 13

In-Reply-To: message from puff!rt4.cs.wisc.edu!blochowi%speedy.wisc.edu@BRL.MIL

The Autumn 89 issue of Call a.p.p.l.e. states in the summary that Orca/C can
produce a source listing ( I assume assembly language source). The assembler
may be more tightly integrated than APW C or Small C, but it is still there
somewhere and it should be possible to flag it to not delete its temp files. 

My understanding of compilers is that any compiler parses the language and
builds either a p-code listing which is then interpreted to run or an assembly
listing which is assembled to machine code. The linker then makes the object
code into a load module for stand alone operation. I had added 1 and 1 and
gotten 2 for my conclusions on Orca/C, my mistake was that it was binary code
and thus should have gotten 10 (clearing the carry bit beforehand of course!).