Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!oddjob!gargoyle!ihnp4!homxb!homxc!lewisd
From: lewisd@homxc.UUCP (David Lewis)
Newsgroups: comp.lang.c
Subject: Re: #include <foo.h> /* comment legal? */
Message-ID: <1775@homxc.UUCP>
Date: Mon, 19-Oct-87 15:34:32 EDT
Article-I.D.: homxc.1775
Posted: Mon Oct 19 15:34:32 1987
Date-Received: Wed, 21-Oct-87 01:21:29 EDT
References: <169@decvax.UUCP> <2205@ihuxy.ATT.COM>
Organization: AT&T Bell Laboratories, Red Hill Site, NJ
Lines: 19
Summary: vice versa

In article <2205@ihuxy.ATT.COM>, chapman@ihuxy.ATT.COM (Chapman) writes:
> In article <169@decvax.UUCP>, minow@decvax.UUCP (Martin Minow) writes:
> > For that matter, may a comment appear in any p.p. statement such as:
> > 	#define	BEAUTY	TRUE	/* All you need to know */
> Whether or not a comment may appear after a #define, what's the worst that
> can happen?  The comment will become part of the definition, but will be
> harmless wherever it is substituted.  (Right, all you C wiz's?)
We hit a major snag with the reverse of this situation: commenting out
preprocessor statements:
  /* commented out
  #define BEAUTY TRUE
  */
Didn't realize that the pre-processor didn't understand comments. 
This happened on a VAX; is it generally the case that BEAUTY will
be defined?
-- 

David B. Lewis    {ihnp4,allegra,ulysses}!homxc!lewisd
201-615-5306 EDT