Path: utzoo!attcan!uunet!kddlab!titcca!sragwa!wsgw!socslgw!diamond!diamond
From: diamond@diamond.csl.sony.junet (Norman Diamond)
Newsgroups: comp.lang.c++
Subject: Re: C++ Comments
Message-ID: <10271@socslgw.csl.sony.JUNET>
Date: 23 May 89 02:26:21 GMT
References: <6957@brunix.UUCP>
Sender: news@csl.sony.JUNET
Reply-To: diamond@csl.sony.junet (Norman Diamond)
Organization: Sony Computer Science Laboratory Inc., Tokyo, Japan
Lines: 19

In article <6957@brunix.UUCP> sdm@cs.brown.edu (Scott Meyers) writes:

>Consider:  //**********************

>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,

Greedy lexing suggests that you should get what you want.  Carelessness
(imprecision) in specifying grammars permits the AT&T interpretation,
but it really should not be allowed, especially if they still can't
parse a+++++b.

--
Norman Diamond, Sony Computer Science Lab (diamond%csl.sony.co.jp@relay.cs.net)
  The above opinions are my own.   |  Why are programmers criticized for
  If they're also your opinions,   |  re-implementing the wheel, when car
  you're infringing my copyright.  |  manufacturers are praised for it?