Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!elroy.jpl.nasa.gov!sdd.hp.com!caen!sol.ctr.columbia.edu!emory!gatech!purdue!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: Comment in #define's
Message-ID: <15087@smoke.brl.mil>
Date: 5 Feb 91 20:00:51 GMT
References: <583@ssp9.idca.tds.philips.nl>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 8

In article <583@ssp9.idca.tds.philips.nl> dolf@idca.tds.philips.nl (Dolf Grunbauer) writes:
>... is the comment in the #define supposed to be removed or not ?
>What does ANSI-C say about this ?

The C standard does not include constraints for "lint" or partial phases
of translation.  Certainly as part of translation by a conforming C
implementation (i.e. compiler), comments get turned into white space
very early in the phases of translation.