Re:Found a bug in the GCC system (not deep, complex or new, ...
by jrockway on Friday May 21, 2010 @12:00PM
(#1367737)
It's strange, though. He includes stdlib.h, and according to my man pages:
Furthermore, here's stdlib.h:
Perhaps it works on my machine because I'm not using an out-of-date version of GCC (gcc (Debian 4.4.4-2) 4.4.4)?
[ Parent
| on HN ]
Re:Found a bug in the GCC system (not deep, complex or new, ...
by jey on Friday May 21, 2010 @12:27PM
(#1367817)
Scroll down in your manpage to the "CONFORMS TO" section. You'll see that strtof was only introduced in C99. This means that stdlib.h tests some macro to determine whether it's in C99 mode before declaring the prototype for strtof.
Re:Found a bug in the GCC system (not deep, complex or new, ...
by bobbyi on Friday May 21, 2010 @12:58PM
(#1367937)
GCC doesn't use C99 mode by default? Is it going to become the default at some point?
Re:Found a bug in the GCC system (not deep, complex or new, ...
by RiderOfGiraffes on Friday May 21, 2010 @01:10PM
(#1367972)
To be fair, recent versions probably do. For reasons I won't (or can't) go into, I have a tendency to be using slightly older systems. That's why I'm more interested in finding out how things can be traced, rather than worrying about this specific mis-match between my expectations and the system's behavior.