Path: utzoo!attcan!uunet!husc6!purdue!haven!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.lang.c
Subject: Re: defining a comment?
Keywords: preprocessor,comments
Message-ID: <13604@mimsy.UUCP>
Date: 18 Sep 88 13:00:17 GMT
References: <5438@techunix.BITNET> <13544@mimsy.UUCP> <779@proxftl.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 32

>In article <13544@mimsy.UUCP> I wrote:
>: >#define STARTCOM /*
>:
>: This is rather dubious.

In article <779@proxftl.UUCP>, bill@proxftl.UUCP (T. William Wells) writes:
>I'd say that
>
>#define STARTCOM /*
>
>just defines STARTCOM as nothing and comments out anything
>following the #define.
>
>I'd also say that any compiler that didn't do this is broken.

Indeed, that is what it must do.  What was missing from
<5438@techunix.BITNET> that prompted my `dubious' was any surrounding
context.  I got the impression that the intent might be to create a
macro that acted like an open-comment `/*' pair, e.g.,

	#define TNEMMOC */
	#define COMMENT /*

	COMMENT
	text to be commented out
	TNEMMOC
	code

which of course does not work.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris