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