Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!purdue!mailrus!cornell!uw-beaver!uw-june!pardo
From: pardo@june.cs.washington.edu (David Keppel)
Newsgroups: comp.std.c
Subject: scope of actual parameters
Message-ID: <8936@june.cs.washington.edu>
Date: 6 Aug 89 21:22:26 GMT
Reply-To: pardo@june.cs.washington.edu (David Keppel)
Organization: University of Washington, Computer Science, Seattle
Lines: 25

My *impression* is that actual parameter names are local to the
function.  My dpANS-compliant compiler (gcc version 1.34) complains on
the following program:

    typedef int foo;
    m (foo){}

    foo.c: parameter name omitted

If I declare the parameter type, then I get a similar complaint.

    typedef int foo;
    m (foo) int foo; {}

    foo.c: parm types given both in parmlist and separately
    foo.c: parameter name omitted

Is this misbehavior of my compiler, or is this compliant behavior?

Please e-mail, I will summarize.

	;-D on  ( A four-poster computer )  Pardo
-- 
		    pardo@cs.washington.edu
    {rutgers,cornell,ucsd,ubc-cs,tektronix}!uw-beaver!june!pardo