Re: what's wrong with atof() and casting?
- From: "Roman Mashak" <mrv@xxxxxxxx>
- Date: Wed, 29 Jun 2005 18:36:24 +0900
Hello, Jack!
You wrote on Wed, 29 Jun 2005 01:52:19 -0500:
??>> Why is compilation and linking of code successful even without
??>> including stdlib.h? At least linking error should arise, no ?
JK> Prior to the 1999 update to the C language standard, it was allowed to
JK> call a function without any sort of declaration or prototype in scope.
[skip]
Moreover, atoi() and atof() are both defined in stdlib.h but only #include
<stdio.h> is put in the source code. Why does compilation succeed anyway?
With best regards, Roman Mashak. E-mail: mrv@xxxxxxxx
.
- Follow-Ups:
- Re: what's wrong with atof() and casting?
- From: Flash Gordon
- Re: what's wrong with atof() and casting?
- References:
- what's wrong with atof() and casting?
- From: XZ
- Re: what's wrong with atof() and casting?
- From: Jack Klein
- Re: what's wrong with atof() and casting?
- From: Roman Mashak
- Re: what's wrong with atof() and casting?
- From: Jack Klein
- what's wrong with atof() and casting?
- Prev by Date: Re: conditional statements
- Next by Date: Re: Aliasing/Torek's strtod() experience
- Previous by thread: Re: what's wrong with atof() and casting?
- Next by thread: Re: what's wrong with atof() and casting?
- Index(es):