Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!apple!motcsd!mcdcup!mcdhup!mcdchg!tellab5!balr!clrcom!rmartin
From: rmartin@clear.com (Bob Martin)
Newsgroups: comp.std.c
Subject: Re: comment style
Message-ID: <1990Dec29.040256.21708@clear.com>
Date: 29 Dec 90 04:02:56 GMT
References: <1990Dec21.014321.5000@kithrup.COM> <26036@uflorida.cis.ufl.EDU> <1990Dec27.215842.23685@ivy.uucp>
Organization: Clear Communications, Inc.
Lines: 25

In article <1990Dec27.215842.23685@ivy.uucp> iverson@ivy.uucp (Tim Iverson) writes:
>Actually, you don't have to put the closing '*/' on the *end* of the line:
>
>/*	e.g. these lines are commented out /* even if they have comments */
>/*	You can also grep for "^/**/" to find where they all are.
>/**/
>

I personally vote for inclusion of the // comment in the ANSI standard.  


Does anybody know what the standard says about nested comments?

i.e.  	/*
		/* is this valid
		/* or will it generate errors 
		/**/

The sun C++ compiler chokes on comments like this, as do a few other C
compilers around.  What is the official stance.
-- 
+-Robert C. Martin-----+:RRR:::CCC:M:::::M:| Nobody is responsible for |
| rmartin@clear.com    |:R::R:C::::M:M:M:M:| my words but me.  I want  |
| uunet!clrcom!rmartin |:RRR::C::::M::M::M:| all the credit, and all   |
+----------------------+:R::R::CCC:M:::::M:| the blame.  So there.     |