Question

While getting started with some VS2005-generated MFC code, I noticed it overrode a method with something like this:

void OnDraw(CDC* /*pDC*/)
{
    ...
    // TODO: Add your code here
}

So of course, as soon as I added something I realized I needed to un-comment the pDC formal argument in order to compile, but I’m confused as to how/why a C++ function can compile (with no warnings) when the formal argument only has a type and not a name:

void foo(int)
{
    int x = 3;
}
int main()
{
    foo(5);
    return 0;
}

Shouldn’t this generate at least a warning (with -Wall or /W4)? It doesn’t seem to. Am I missing something? Is there a case where this is useful or is it just because the compiler can’t tell the difference between a function declaration (only types required) and a definition (fully specified) until after the line has been processed?

Answer 1

Because sometimes you have a parameter that’s required by an interface but the function doesn’t use it. Maybe the parameter is no longer necessary, is only necessary in other functions that must use the same signature (especially so they can be called through pointers) or the functionality hasn’t been implemented yet. Having parameters that aren’t used can be particularly common in generated or framework code for this reason (and that’s probably why the MFC generated code has the name commented out).

As to why there’s no warning – I guess it’s because whether this is a problem is a subjective thing and other people (particularly compiler implementers) don’t see it as a problem. Once you actually go to use the parameter, you’ll get the compiler to complain if you forget to uncomment the name so you get the compiler complaining only when you really need it to (the compiler’s version of the agile YAGNI: “You Aren’t Gonna Neet It” philosophy).

The opposite does seem to generally occur when you crank up warnings – named parameters that aren’t used generate warnings – again that’s probably why the generated function has the name commented out.