[ Bellevue: Wording is aleady present in various standards, and no-one has come forward with wording. Suggest a formal paper rather than a defect report is the correct way to proceed. ]

[ Post-Kona: Alisdair request Open. A good example of the problem was a discussion of the system error proposal, where it was pointed out an all-caps identifier starting with a capital E conflicted with reserved macro names for both Posix and C. I had absolutely no idea of this rule, and suspect I was not the only one in the room.

Resolution will require someone with access to all the listed documents to research their respective name reservation rules, or people with access to specific documents add their rules to this issue until the list is complete. ]

[ Kona (2007): Recommend NAD. No one has identified a specific defect, just the possibility of one. ]

[intro.refs] Normative references

The following standards contain provisions which, through reference in this text, constitute provisions of this Interna- tional Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this International Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. Members of IEC and ISO maintain registers of currently valid International Standards.

• Ecma International, ECMAScript Language Specification, Standard Ecma-262, third edition, 1999.
• ISO/IEC 2382 (all parts), Information technology - Vocabulary
• ISO/IEC 9899:1990, Programming languages - C
• ISO/IEC 9899/Amd.1:1995, Programming languages - C, AMENDMENT 1: C Integrity
• ISO/IEC 9899:1999, Programming languages - C
• ISO/IEC 9899:1999/Cor.1:2001 Programming languages - C
• ISO/IEC 9899:1999/Cor.2:2004 Programming languages - C
• ISO/IEC 9945:2003, Information Technology-Portable Operating System Interface (POSIX)
• ISO/IEC 10646-1:1993 Information technology - Universal Multiple-Octet Coded Character Set (UCS) - Part 1: Architecture and Basic Multilingual Plane

I'm not sure how many of those reserve naming patterns that might affect us, but I am equally sure I don't own a copy of any of these to check!

The point is to list the reserved naming patterns, rather than the individual names themselves - although we may want to list C keywords that are valid identifiers in C++ but likely to cause trouble in shared headers (e.g. restrict)