From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Fw: Possible GCC Bug
Date: 17 Apr 2000 11:06:39 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 23
Message-ID: <8der7v$hh6$1@nets3.rz.RWTH-Aachen.DE>
References: <000f01bfa673$a9e573e0$0100a8c0 AT amanda>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 955969599 17958 137.226.32.75 (17 Apr 2000 11:06:39 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 17 Apr 2000 11:06:39 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

>> 0xff, // 00000000  // \
>> 0x60, // 01100000
[...]
>> I think gcc's scanner is interpreting the slash as a special character, 
>> rather than just skipping it as it should as it is part of a single 
>> line comment.

That interpretation of what it should do is wrong. The C99 draft
(which is the only useable reference about // comments in C programs)
clearly demonstrates it in one of its examples in section 6.4.9:

               //\
               i();                     // part of a two-line comment

Technically spoken: backslash-newline removal happens before the
source is parsed for comments or any other tokens. This is so even in
old-style ANSI C.



-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.