Xref: utzoo comp.object:1679 comp.lang.c++:9263
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!aplcen!uunet!hsi!stpstn!lerman
From: lerman@stpstn.UUCP (Ken Lerman)
Newsgroups: comp.object,comp.lang.c++
Subject: Re: What is Objective C?
Keywords: C++, Objective C
Message-ID: <5498@stpstn.UUCP>
Date: 27 Aug 90 22:11:32 GMT
References: <3864@bingvaxu.cc.binghamton.edu> <4998@pegasus.ATT.COM> <11233@alice.UUCP>
Reply-To: lerman@stpstn.UUCP (Ken Lerman)
Organization: The Stepstone Corporation, Sandy Hook, CT 06482
Lines: 26

In article <11233@alice.UUCP> ark@alice.UUCP (Andrew Koenig) writes:
->I would like to add one thing to Tony Hansen's remarks.
->
->Cfront is a compiler that works roughly like this:
->
->	1. Read and parse a C++ program into an internal representation.
->
->	2. Walk through the internal representation translating the
->	   parts of C++ that aren't in C into the corresponding C code.
->
->	3. Print out C source code corresponding to the internal representation.
->

Ditto for Objective-C.  Except that for some constructs, steps 2 and 3
are done in parallel.  (substituting Objective-C for C++, of course)

[...stuff deleted...]
>-- 
>				--Andrew Koenig
>				  ark@europa.att.com

Disclaimer: Although I ought to know, since I look at the compiler
source every day, these opinions (do they look like facts? ) are mine
and I represent myself.

Ken Lerman