Path: utzoo!attcan!uunet!lll-winken!elroy.jpl.nasa.gov!sdd.hp.com!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: Another sizeof question
Message-ID: <14343@smoke.brl.mil>
Date: 6 Nov 90 03:42:40 GMT
References: <2638@cirrusl.UUCP> <1990Nov1.162942.3609@zoo.toronto.edu> <2654@cirrusl.UUCP>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 11

In article <2654@cirrusl.UUCP> dhesi%cirrusl@oliveb.ATC.olivetti.com (Rahul Dhesi) writes:
>Because at the time that ANSI was in the middle of developing the
>standard, so far as I could tell, all existing substantially complete
>implementations of K&R's C provided a way of doing preprocessing only.

There were at least a couple of commercial C compilers with "tokenizing"
preprocessors; they may have allowed the result of preprocessing to be
converted back into some form of source code for people who requested
such a facility or they may not (I don't recall).  In any case, we have
been telling people for years that if they want a macro processor they
should use something like "m4" rather than rely on cpp.