Date: Sat, 24 Jan 1998 19:00:23 -0500 (EST) Message-Id: <199801250000.TAA02614@delorie.com> From: DJ Delorie To: andrewc AT rosemail DOT rose DOT hp DOT com CC: djgpp-workers AT delorie DOT com In-reply-to: <199801242352.AA097625925@typhoon.rose.hp.com> (message from Andrew Crabtree on Sat, 24 Jan 1998 15:52:05 PST) Subject: Re: gcc 2.8.0 Precedence: bulk > Hmm - as in stop compiling or not working at all at finding the file? > Thats definitely not the behaviour now. If cpp left \ in the # lines, gcc would abort because it didn't recognize the escape sequence (i.e. like '\n'). > The comments from the cygwin file seemed to indicate > that it would just enable '\' in addition to '/'. This change was > probably made after egcs split off so there is a chance its not > in the gcc sources. It would be 1 line near the bottom of the 'xm' file. If this is the case, OK. I think the important issue is what gcc et al *print*; what it accepts is a different issue - it *should* accept both (except in strings, where \n would be newline, so '\' should be avoided).