From: "-hs-" <email DOT invalid AT server DOT invalid>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Possible GCC Bug
Date: Sat, 15 Apr 2000 18:18:56 +0200
Lines: 43
Message-ID: <8da4pj$huj$1@news4.isdnet.net>
References: <000f01bfa673$a9e573e0$0100a8c0 AT amanda>
NNTP-Posting-Host: r76m230.cybercable.tm.fr
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Trace: news4.isdnet.net 955815539 18387 195.132.76.230 (15 Apr 2000 16:18:59 GMT)
X-Complaints-To: abuse AT isdnet DOT net
NNTP-Posting-Date: 15 Apr 2000 16:18:59 GMT
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Nick Fleming a écrit dans le message
<000f01bfa673$a9e573e0$0100a8c0 AT amanda>...
>
<...>

>> 0xff, // 00000000  // \
>> 0x60, // 01100000

<...>

>> In the above snippet of code, the second group of  bytes has a row
missing when
>> compiled.. To correct it I have to write the first line as follows:
>>
>> 0xff, // 00000000  // '\'
>>
>> 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.


No bug. The \ character allows to cut the lines properly.

This is (ugly but) valid C :

i\
n\
t
main(v\
oid)
{
   re\
turn 0;
}

--
-hs- "Stove"
CLC-FAQ: http://www.eskimo.com/~scs/C-faq/top.html
ISO-C Library: http://www.dinkum.com/htm_cl
"Really?  When run on my machine, a printed copy of the C FAQ leaps
from the monitor and whacks me over the head.." -- Chris Mears CLC