Re: 64bits and a problem with pointers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2010/12/2 NicolÃs Dato <nicolas.dato@xxxxxxxxx>:
>
> why does this happen? because when gcc doesn't find the function getpointer(), I think it
> "declares" it something like this
> int getpointer(...);
>
> [...]
>
> The question is... is this a 100% programmer problem? or should gcc warn you also when you
> don't use the -Wall option?
>

This behaviour is as specified by the C standard -- an undeclared
function is called as though it took a variadic argument list and
returned int.  And since the linker has no type information, it cannot
catch the mismatch.

~ Scott



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux