🚀 go-pugleaf

The point I think he was trying to make is that it wasn't a floating point
number? 

It was the hex integer negative 0x2E, plus the integer value zero. 

The compiler is interpreting it as a floating point number in exponential
form. It shouldn't be doing so since the 0x should indicate that the number
is in hex. Basically it looks like the "0x" is having lower precedence than
the "E" for exponential numbers.

-- Nathan

| It's not a bug. The ANSI C standard requires
| that a floating point constant should be specified
| using decimal digits only.
| 
| The -0x2E+0 constant uses hexdecimal digits. Other 
| compilers which allow it deviate from the standard.
| 
| Bye,
| Eyal
| 
| 
| 
| : Date: Sun, 17 Nov 96 08:40:14 IST
| : From: orid@taux01.nsc.com (Ori Dvir)
| : Message-Id: <9611170640.AA00525@tasu5k.nsc.com>
| : To: bug-gcc@prep.ai.mit.edu
| : Subject: Parse error?
| : Status: R
| : 
| : Hi,
| : 
| : I have a problem of parsing:
| : when i compile this file :
| : 
| : main(){
| : int a;
| : a = 0x2e+0;
| : }
| : 
| : >gcc t.c
| : 
| : I get :
| : 
| : t.c: In function `main':
| : t.c:6: garbage at end of number
| : 
| : The expresion should stand for: 0x2e + 0 ( hex + decimal ).
| : 
| : I'm using gcc version 2.7.2 on Sun meachines.
| : 
| : Thanks,
| : Ori dvir :  orid@taux01.nsc.com.il
| :  
| :

------------------------------------------------------------
Nathan Neulinger                  Univ. of Missouri - Rolla
EMail: nneul@umr.edu                  Computing Services
WWW: http://www.umr.edu/~nneul      SysAdmin: rollanet.org