Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!lll-tis!ames!hao!gatech!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!uiucdcs!uiucdcsp!gillies
From: gillies@uiucdcsp.cs.uiuc.edu
Newsgroups: comp.sys.mac
Subject: Re: LightSpeed C, and C++
Message-ID: <76000138@uiucdcsp>
Date: 25 Feb 88 01:33:00 GMT
References: <6815@drutx.ATT.COM>
Lines: 7
Nf-ID: #R:drutx.ATT.COM:6815:uiucdcsp:76000138:000:377
Nf-From: uiucdcsp.cs.uiuc.edu!gillies    Feb 24 19:33:00 1988


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).

Maybe LighspeedC could support plugging in your own custom
preprocessor.  Slower performance would probably be o.k.  But then I
could plug in a C++ preprocessor to LighspeedC, and have LighspeedC++!!!