CODEWITHSUNDEEP
c
user823738
user823738

Reputation: 17521

Why prototype and definition of a function in C may differ?

I'm wondering why this will compile:

int test();

int main() { return test((void*)0x1234); }
int test(void* data) { return 0; }

Why won't the compiler emit any error/warning about that (I tried clang, gcc)? If I change the return value it won't compile - but the arguments may differ?!

Upvotes: 20

Views: 521

Answers (2)

Paul R
Paul R

Reputation: 212959

If you change:

int test();

to:

int test(void);

you will get the expected error:

foo.c:4: error: conflicting types for ‘test’
foo.c:1: error: previous declaration of ‘test’ was here

This is because int test(); simply declares a function which takes any parameters (and is therefore compatible with your subsequent definition of test), whereas int test(void); is an actual function prototype which declares a function which takes no parameters (and which is not compatible with the subsequent definition).

Upvotes: 28

ouah
ouah

Reputation: 145829

 int test();

in a function declaration, no parameter means the function takes an unspecified number of arguments.

This is different than

 int test(void);

which means the function takes no argument.

A function declaration with no parameter is the old C style of function declaration; C marks this style as obsolescent and discourages its use. In short, don't use it.

In your case, you should use a function declaration with the correct parameter declaration:

 int test(void *data);

Upvotes: 15

Related Questions