Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ukma!husc6!endor!siegel
From: siegel@endor.harvard.edu (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Object Oriented C for the Mac
Message-ID: <2286@husc6.harvard.edu>
Date: 25 Jul 89 22:55:52 GMT
References: <44053@tiger.oxy.edu> <227700016@uxa.cso.uiuc.edu> <1562@garcon.cso.uiuc.edu>
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Organization: Symantec Language Products Group
Lines: 30

In article <1562@garcon.cso.uiuc.edu> emb90619@uxa.cso.uiuc.edu (Eric M Berdahl) writes:
>In article <227700016@uxa.cso.uiuc.edu> jpd00964@uxa.cso.uiuc.edu writes:

>Not exactly, C++ is also a preprocesor, just different enough to be considered
>a different language.  In fact, if you look at most any C++ implementation,
>you will find a cfront "preprocessor" and a C compiler are the basic pieces
>of the system.

	Not exactly. There are pure C++ compilers in existence, but most
implementors find it simpler to license cfront from AT&T and have it generate
code for their own C compilers.

	IMHO this is a real deficiency, because it's a realy slowdown to
the compiler - can you imagine how slow LightspeedC would be if there
were a C++ preprocessor tacked onto it? Also, using a preprocessor
makes it very difficult to offer source-level debugging for the 
preprocessed code.

		--Rich
~~~~~~~~~~~~~~~
 Rich Siegel
 Staff Software Developer
 Symantec Corporation, Language Products Group
 Internet: siegel@endor.harvard.edu
 UUCP: ..harvard!endor!siegel

"When it comes to my health, I think of my body as a temple - or at least
a moderately well-managed Presbyterian youth center." - Emo Phillips

~~~~~~~~~~~~~~~