Re: warning: '/*' within comment

Article View: comp.std.c

Article #1389

#1389

From: Adam Stoller
Date: Mon, 04 Jun 1990 12:31

20 lines
977 bytes

Use the alternate style of commenting - i.e. instead of:

/*
Sample usage:
	mkscript src/*.c src/*.h src/makefile man/* readme > dist.txt
*/

Try:

#if 0
Sample usage:
	mkscript src/*.c src/*.h src/makefile man/* readme > dist.txt
#endif /* 0 */

I believe that this should pass through lint, compiler, linker, etc.
without any problem - and not conflict with ANSI in any way (at least
none that I recall reading)

--fish
( I'm not an authority - and I don't play one on tv )

Technical Details

Message-ID: <AaOZGd_00as98coVU9@andrew.cmu.edu>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!watserv1!watmath!att!ucbvax!tut.cis.ohio-state.edu!pt.cs.cmu.edu!andrew.cmu.edu!ghoti+

References: <1990Jun1.200433.6919@druid.uucp>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!watserv1!watmath!att!ucbvax!tut.cis.ohio-state.edu!pt.cs.cmu.edu!andrew.cmu.edu!ghoti+
From: ghoti+@andrew.cmu.edu (Adam Stoller)
Newsgroups: comp.std.c
Subject: Re: warning: '/*' within comment
Message-ID: <AaOZGd_00as98coVU9@andrew.cmu.edu>
Date: 4 Jun 90 12:31:37 GMT
References: <1990Jun1.200433.6919@druid.uucp>
Organization: Information Technology Center, Carnegie Mellon, Pittsburgh, PA
Lines: 20
In-Reply-To: <1990Jun1.200433.6919@druid.uucp>

Reply to Parent Message