Question

I have a very simple Objective-C sample

#import <Foundation/Foundation.h>

int littleFunction();

int main (int argc, const char * argv[])
{

    NSAutoreleasePool * pool 
    = [[NSAutoreleasePool alloc] init];

    // insert code here...
    NSLog(@"Hello, World!");

    [pool drain];
    return 0;
}

int littleFunction()
{
    return 0;
}

With this code I get a “no previous prototype for function” warning for littleFunction but as you can all see there is a declaration before main. What is wrong here? It seem the compiler is unable to match the declaration with the function implementation.

If I change both like this:

int littleFunction(void)

it works perfectly.
I am using the latest Xcode 4

Answer 1

In C, int littleFunction(); is not really a prototype. It doesn’t specify how many (or what sort of) parameters the function accepts.

The actual wording in C99 is in §6.7.5.3 item 14:

An identifier list declares only the identifiers of the parameters of the function. An empty list in a function declarator that is part of a definition of that function specifies that the function has no parameters. The empty list in a function declarator that is not part of a definition of that function specifies that no information about the number or types of the parameters is supplied.¹²⁴

The footnote refers to this section in the Future language directions:

6.11.6 Function declarators
The use of function declarators with empty parentheses (not prototype-format parameter
type declarators) is an obsolescent feature.

(Note: this is still present in the C11 draft I have (n1570).)

Back in §6.7.5.3, item 10:

The special case of an unnamed parameter of type void as the only item in the list
specifies that the function has no parameters.

So you have to explicitly specify int foo(void); if you want to prototype a function that doesn’t take parameters. Objective-C has the same rules.