Benno wrote: > True, I think that gcc treating parameter names in function > declarations as `public' is total arse though.
OK, you are suggesting that the compiler should treat parameter names and function names as being in separate name spaces. If you then have a function named foo and parameter named foo and you use foo in your function? How does the compiler distinguish between foo the parameter and foo the function? C++ has the scope resolution operator ::, but C has no such mechanism. > Until the next time you decide to create a private function that > happens to have the same name as an argument in some header file. How often does this happen to you? I get it with index, but thats the only one I can remember. > Or I fall back to the last line of defense: index() isn't the C > standard and I want to use it as a variable name damnit! Yes, I agree that that particular piece of BSD brain damage is a PITA, but how hard is it to use indx instead of index? > P.S: Thats all from me on this thread... I'm happy to leave it at the > we disagree stage ;) If you get name clashes on anything other than index, I'd really like to know about it. After that we can agree to disagree. Erik -- +-----------------------------------------------------------+ Erik de Castro Lopo [EMAIL PROTECTED] (Yes it's valid) +-----------------------------------------------------------+ "Microsoft, and other companies with shoddy security, ....." -- Bruce Schneier, cryto-guru, to a US Senate committee. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
