Path: utzoo!attcan!uunet!snorkelwacker!bu.edu!mirror!necntc!necssd!harrison
From: harrison@necssd.NEC.COM (Mark Harrison)
Newsgroups: comp.std.c
Subject: Re: warning: '/*' within comment
Message-ID: <371@necssd.NEC.COM>
Date: 6 Jun 90 14:37:26 GMT
References: <1990Jun1.200433.6919@druid.uucp> <AaOZGd_00as98coVU9@andrew.cmu.edu> <16786@haddock.ima.isc.com>
Organization: NEC America Inc. SSD, Irving, TX
Lines: 25

In article <16786@haddock.ima.isc.com>, karl@haddock.ima.isc.com
 (Karl Heuer) writes:
> More generally, `#if 0...#endif' should not be considered a `comment', except
> in the sense of `commenting out code'.  The contents are still lexed into C
> tokens, which is why it's also illegal to say
> 	#if 0
> 	The compiler won't like this
> 	#endif
> 
> Karl W. Z. Heuer (karl@ima.ima.isc.com or harvard!ima!karl), The Walking Lint

Are you sure about this?  I tried your example, and it both compiled and
linted.  If this is true, then the following should also not work:

#if MICROSOFT
extern far char * x;  /* however it's done */
#endif

#if VMS
extern char * x$something;  /* however it's done */
#endif
-- 
Mark Harrison             harrison@necssd.NEC.COM
(214)518-5050             {necntc, cs.utexas.edu}!necssd!harrison
standard disclaimers apply...