macro parameter names

[Richard H. Gumpertz]

In article <1989Nov27.223210.29880 at utzoo.uucp> henry at utzoo.uucp (Henry Spencer) writes:
>In article <18672 at watdragon.waterloo.edu> afscian at 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 at uunet.uu.NET -or- ...uunet!amgraf!cpsolv!rhg |
| Computer Problem Solving, 8905 Mohawk Lane, Leawood, Kansas 66206-1749      |
===============================================================================