Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!husc6!cmcl2!philabs!micomvax!musocs!mcgill-vision!mouse
From: mouse@mcgill-vision.UUCP (der Mouse)
Newsgroups: comp.unix.questions
Subject: Re: Teaching Assembler on VAX (BSD 4.3)
Message-ID: <787@mcgill-vision.UUCP>
Date: Sun, 31-May-87 03:10:46 EDT
Article-I.D.: mcgill-v.787
Posted: Sun May 31 03:10:46 1987
Date-Received: Thu, 11-Jun-87 02:57:23 EDT
References: <7447@brl-adm.ARPA> <1658@tekcrl.TEK.COM> <5874@brl-smoke.ARPA>
Organization: McGill University, Montreal
Lines: 21

In article <5874@brl-smoke.ARPA>, gwyn@brl-smoke.ARPA (Doug Gwyn ) writes:
> Please don't use /lib/cpp except as part of /bin/cc.
> It is not intended for use as a general macro processor and may
> indeed go away some day.

A long way off.  Too many things use /lib/cpp for it to disappear soon.
Of course you are correct; one *should* use the -E option to cc, which
is documented.  I suspect the reason for using /lib/cpp is that cc -E
won't work unless you have a file with a name ending in .c (no pipe
input, no .s files....).

> If you need a macro processor on UNIX, use m4.

Except that m4 and cpp address things rather differently.  Until you
write a macro package for m4 that makes it behave like cpp (and I mean
exactly like cpp), people will continue to use cpp.  Existing code and
existing skills ensure this.

					der Mouse

				(mouse@mcgill-vision.uucp)