On Wed, Apr 25, 2001 at 09:50:22PM +1000, Kevin Easton wrote:
> Of course, if you don't include the declaration of atof (which is what's in
> stdlib.h), then the compiler can't check the type and number of parameters,
> and the type of the return value of the function.
When I was checking return t
>
> Unless I compile with -Wall, following code compiles with no warning
> with "gcc -g -o example example.c".
>
> How should I tell that this code is broke after compile?
> --
> # include
> /*# include */ /*Not to have this for atof is the bug*/
> int main(int argc, char **argv) {
> flo
inal Message -
From: "Osamu Aoki" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, April 25, 2001 6:59 PM
Subject: howto identify missing stdlib.h after compile?
> Unless I compile with -Wall, following code compiles with no warning
> with "gcc -g -o example
Unless I compile with -Wall, following code compiles with no warning
with "gcc -g -o example example.c".
How should I tell that this code is broke after compile?
--
# include
/*# include */ /*Not to have this for atof is the bug*/
int main(int argc, char **argv) {
float x=0;
x=atof("123.4
4 matches
Mail list logo
