This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC/EGCS parser bug
- To: amylaar at cygnus dot co dot uk
- Subject: Re: GCC/EGCS parser bug
- From: "Martin v. Loewis" <martin at mira dot isdn dot cs dot tu-berlin dot de>
- Date: Tue, 16 Feb 1999 01:18:35 +0100
- CC: zack at rabi dot columbia dot edu, Joachim dot Hollman at front dot se, egcs at egcs dot cygnus dot com
- References: <199902142129.VAA02537@phal.cygnus.co.uk>
> The scope of X is inside the function parameter list. Thus, when X is used
> the second time, the first use is out of scope, hence no clash.
This is what I thought. Then what about the original example?
typedef void (*func)(int);
void f(int i1, void (*func)(void *, void *), int i2);
Shouldn't the prototype of f open a new scope, shadowing the previous
(global) definition of func? Shouldn't that happen regardless of whether
the previous definition was a typedef or an object?
Martin