Path: utzoo!attcan!uunet!brunix!sdm
From: sdm@cs.brown.edu (Scott Meyers)
Newsgroups: comp.lang.c++
Subject: C++ Comments
Message-ID: <6957@brunix.UUCP>
Date: 21 May 89 23:59:37 GMT
Sender: news@brunix.UUCP
Reply-To: sdm@cs.brown.edu (Scott Meyers)
Organization: Brown University Department of Computer Science
Lines: 18

Consider the following C++ source line:

    //**********************

How should this be treated by the C++ compiler?  The GNU g++ compiler
treats this as a comment-to-EOL followed by a bunch of asterisks, but the
AT&T compiler treats it as a slash followed by an open-comment delimiter.
I want the former interpretation, and I can't find anything in Stroustrup's
book which indicates that any other interpretation is to be expected.

Actually, compiling -E quickly shows that the culprit is the preprocessor,
so my questions are:
    1.  Is this a bug in the AT&T preprocessor?  If not, why not?  If so,
    	will it be fixed in 2.0, or are we stuck with it?
    2.  Is it a bug in the GNU preprocessor?  If so, why?

Scott Meyers
sdm@cs.brown.edu