macro parameter names

[Henry Spencer]

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.
-- 
That's not a joke, that's      |     Henry Spencer at U of Toronto Zoology
NASA.  -Nick Szabo             | uunet!attcan!utzoo!henry henry at zoo.toronto.edu