Path: utzoo!mnetor!uunet!husc6!uwvax!oddjob!gargoyle!ihnp4!inuxc!iuvax!viking
From: viking@iuvax.cs.indiana.edu
Newsgroups: comp.sys.mac
Subject: Re: LightSpeed C, and C++ (what the
Message-ID: <3600023@iuvax>
Date: 7 Mar 88 23:11:00 GMT
References: <6894@drutx.ATT.COM>
Organization: Indiana University CSCI, Bloomington
Lines: 23
Nf-ID: #R:drutx.ATT.COM:6894:iuvax:3600023:000:1013
Nf-From: iuvax.cs.indiana.edu!viking    Mar  7 18:11:00 1988


>>From article <702@hqda-ai.UUCP>, by arbaugh@hqda-ai.UUCP (Bill Arbaugh):
>> In article <76000138@uiucdcsp>, gillies@uiucdcsp.cs.uiuc.edu writes:

>>> I believe that C++ was designed so it could be implemented with a
>>> preprocessor (a more sophisticated proprocessor than M4, which brings
>>> #include and #define to C programming).

>> The C++ by AT&T is somewhat like a preprocessor, but it also plays
>> with the objects upon exit and etc.  

> But I think that if you have a look at what the C++ compiler really
> does, you will be more than willing to call it a compiler.  If you can
> get a look at source, you'll be the more sure.

Maybe so, but when Brian Kernighan lectured about C++ at Purdue University
back in 1984, he described as a pre-processor too.

---
Joni Backstrom               "Yah sure...we gonna have fun, you bet!"
Computer Science Department
Indiana University           ARPA: viking@iuvax.cs.indiana.edu
Bloomington, IN  47405       UUCP: {pyramid,ihnp4,pur-ee,rutgers}!iuvax!viking