Thread: f() or f(void)

Should i use f() or f(void) to indicate that the function doesn't take any argument. I read in an C++ FAQ that it considered to be a bad programming style in C++ but what with C ? I also know that if f() is used it is assumed to take any number of int arguments.
Actually the FAQ confused me, although i prefer to use f(void).
Thanks

I would say that f() is by far the most common, including in (eg) C library sources.

Originally Posted by MK27

I would say that f() is by far the most common, including in (eg) C library sources.

It does make a difference though. If you declare:

Code:

void f();

And then somebody calls:

Code:

f( 1, 2, 3, "foo" );

The compiler will not complain. The only time I use such "pure variadic" functions is in the context of a function pointer. I don't ever declare real functions that way. If it really takes no arguments, you should say "void."

Well, this was good execise since i never checked this before. It seems that the compile is confused whether to call the function f with the an argument even tho the function takes no argumrnts. It is much to specify the void atleast in C to say that the function takes no arguments. If not its an undefined behaviour.

Code:

#include <stdio.h>

void f()
{
     printf("helloe");
}

int main()
{
    f(10);
    
    getchar();
    return 0;
}
/* my output
helo
*/

I am above code, i was expected an error. But the compiler dint complain and it was happy to execute. But when places a void int he f function. It did warn me!

-ssharish

Thanks brewbuck. Your example was nice. As ssharish said my compiler too didn't throw any error but it did warn me too.
Also thanks itCbitC for the faq. That FAQ explained it nicely.

Originally Posted by ssharish2005

Code:

#include <stdio.h>

void f()
{
     printf("helloe");
}

int main()
{
    f(10);
    
    getchar();
    return 0;
}
/* my output
helo
*/

Care to rethink that?


Quzah