Clyde, > On Fri, Jul 15, 2005 at 07:59:06AM +0200, 42Bastian Schick wrote: > > I read the manual now, but still I think 0x3e+2 must be > compiled and > > give 0x40. > > I disagree with the GCC implementers on this, but nonetheless > a strict interpretation of the ANSI/ISO standard for C does > mean that 0x3e+2 is parsed as an invalid floating point > number. My view is that a more intelligent interpretation > would be preferable, but that's not what GCC does. Even under C90, 0x3e+2 is a good preprocessing number but a bad C floating point literal and *must* be reported as an error! -- Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks for MSP430, ARM, AVR and now MAXQ processors
Message
RE: [lpc2000] Bug in gcc parser
2005-07-15 by Paul Curtis
Attachments
- No local attachments were found for this message.