Path: utzoo!utgpu!water!watmath!clyde!att!cbnews!lvc From: lvc@cbnews.ATT.COM (Lawrence V. Cipriani) Newsgroups: comp.lang.c Subject: Re: C compilers with integrated preprocessors Keywords: preprocessor,comments Message-ID: <1252@cbnews.ATT.COM> Date: 20 Sep 88 16:53:44 GMT References: <3999@bsu-cs.UUCP> <33440@cca.CCA.COM> <1292@scolex> Reply-To: lvc@cbnews.ATT.COM (Lawrence V. Cipriani) Organization: AT&T Bell Laboratories, Columbus Lines: 15 >In article <3999@bsu-cs.UUCP> dhesi@bsu-cs.UUCP (Rahul Dhesi) writes: >It is agreed that a Real ANSI-conforming C compiler might not supply a >separate preprocessor pass, but who cares? Such a C compiler would be >an instant commercial failure. As long as one can access "the proprocessor" via a command line option (or whatever) I don't think it matters much if it is a *separate program* or not. There are many many applications that use the C preprocessor that are not C programs. There is even a "calendar" program that uses the C preprocessor. If I couldn't access the preprocessor separately from the rest of the compilation then I'll just keep the preprocessor I already use. -- Larry Cipriani, AT&T Network Systems, Columbus OH, cbnews!lvc lvc@cbnews.ATT.COM