This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Should we make "implicit declaration of function" a mandatory warning?
On Mon, Jan 15, 2001 at 10:29:46AM +0100, Jamie Lokier wrote:
> Joseph S. Myers wrote:
> > The most likely case these days is actually probably going to be that the
> > program is a quick hack (otherwise -Wall should be used), and the return
> > value isn't being used so the programmer doesn't really care.
>
> Perhaps there should be a warning "return type `int' of implicitly
> declared function `exp' may be incorrect" iff the return value is
> not simply ignored discarded.
But it's not just the return type that's likely to cause a problem, as
I understand it - the most frequent place I see this error is actually
floats being (or not being) promoted to doubles in arguments.
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| dan@debian.org | | dmj+@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/