Re: const oddity in decorated names

If I declare the functions

void foo(int bar[])
void bar(int * bar)

then I expect them to behave the same way - and indeed they do in most
cases. I have give these functions these (admittedly meeningless)
implementation:

__declspec(dllexport) void foo(int bar[]) { bar = NULL; }
__declspec(dllexport) void bar(int * bar) { bar = NULL; }

The program compiles. If I look at the decorated names of the exported
names
in the dll they aren't the same though. foo gets a decorated names that
indicates that it was declared as
void foo(int * const bar).
But since the program above compiled that is obviously not the case.

I'll have admit that the difference between "int *" and "int * const" in a
function argument is irrelevant to the caller of the function, but is
there a
reason for this oddity, or is this just a mistake?