Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!amgraf!cpsolv!rhg
From: rhg@cpsolv.UUCP (Richard H. Gumpertz)
Newsgroups: comp.std.c
Subject: Re: macro parameter names
Message-ID: <457@cpsolv.UUCP>
Date: 28 Nov 89 14:13:05 GMT
References: <11160@riks.csl.sony.co.jp> <1989Nov22.222413.3874@utzoo.uucp> <11188@riks.csl.sony.co.jp> <11685@smoke.BRL.MIL> <18672@watdragon.waterloo.edu> <1989Nov27.223210.29880@utzoo.uucp>
Reply-To: rhg@cpsolv.uucp (Richard H. Gumpertz)
Organization: Computer Problem Solving, Leawood, Kansas
Lines: 18

In article <1989Nov27.223210.29880@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
>In article <18672@watdragon.waterloo.edu> afscian@violet.waterloo.edu (Anthony Scian) writes:
>>What about the library prototypes that are coded "int foo( int x, int y )"
>>when they should be "int foo( int __x, int __y )"?
>
>Can you cite chapter and verse for why the parameter names need to be in
>the implementation name space?  They don't interfere with user identifiers
>of the same name, and it doesn't look to me as if user identifiers of the
>same name can interfere with them.

What if "x" or "y" is #defined by the program before the site of the
declaration of foo?

-- 
===============================================================================
| Richard H. Gumpertz rhg%cpsolv@uunet.uu.NET -or- ...uunet!amgraf!cpsolv!rhg |
| Computer Problem Solving, 8905 Mohawk Lane, Leawood, Kansas 66206-1749      |
===============================================================================