Fuction pointers - Is this legal C?

[David Scarlett]

Can anyone tell me whether the following is legal C?

int foo(int);
int bar(int (*)(int));

int main(void)
{
int x;

x = bar(&foo);

return 0;
}

int bar(int (*foo)(int))
{
/* ... */
}

I had some similar code which compiled fine using 'gcc -Wall', but I'm
concerned about what would happen if I called 'foo' from withing 'bar'.
Would it use the pointer it is passed, or the function declared at the
start, if they were different functions? Or is this undefined
behaviour? What if I used the dereferencing operator when calling foo?

I've changed the name of the pointer 'bar' recieves just to be safe,
but I'm still curious as to what the effects of this sort of code would
be...
Thanks.

--
David Scarlett

dscarlett@_ _ _ _ _ _ _ _
_ _ _ _ _ optusnet.com.au

[Kip Neuhart]

"David Scarlett" <lo**@my.signature> wrote

Can anyone tell me whether the following is legal C?
<snip code>
Would it use the pointer it is passed, or the function declared at the
start, if they were different functions? Or is this undefined
behaviour? What if I used the dereferencing operator when calling foo?

The global name is hidden by the local parameter name. Any references to foo
will act on the parameter, which is standard and correct behavior. It
doesn't matter at all whether you dereference the pointer when calling foo
(except for older compilers that require it), both are allowed and will
still reference the parameter.

[Barry Schwarz]

On 02 May 2004 09:14:18 GMT, David Scarlett <lo**@my.signature> wrote:

Can anyone tell me whether the following is legal C?

int foo(int);
int bar(int (*)(int));

int main(void)
{
int x;

x = bar(&foo);
The & is unnecessary. A function name without the parenthesized
argument list is the syntactical representation of the address of the
function.

return 0;
}

int bar(int (*foo)(int))
{
/* ... */
}

I had some similar code which compiled fine using 'gcc -Wall', but I'm
concerned about what would happen if I called 'foo' from withing 'bar'.
Would it use the pointer it is passed, or the function declared at the
start, if they were different functions? Or is this undefined
behaviour? What if I used the dereferencing operator when calling foo?

I've changed the name of the pointer 'bar' recieves just to be safe,
but I'm still curious as to what the effects of this sort of code would
be...
Thanks.

<<Remove the del for email>>