[Mingw-notify] [ mingw-Bugs-1424461 ] Avoidable namespace pollution in win32api

[SourceForge.net <no...@so...>]

Bugs item #1424461, was opened at 2006-02-05 10:26
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1424461&group_id=2435

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: w32api
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Ron (ronl)
Assigned to: Nobody/Anonymous (nobody)
Summary: Avoidable namespace pollution in win32api

Initial Comment:
Hi,

Could we please uglify the #define'd "psuedo modifiers",
IN, OUT, and OPTIONAL (perhaps others) in win32api?

It is the latter which has burned the code I'm presently
porting, being the name of an enum, nested in a class,
in a named namespace.  It appears even the gcc source
dist that mingw releases uses OPTIONAL as an enum
value, so I'm not alone in thinking it is fair game in
my own
code.

I can't find anything that indicates this is for
compatibility with "native stupidity", and they are all
defined to nothing, so the name seems quite arbitrary and
safe to change to something a little less collision prone.

I can whip up a patch to fix this if we can agree on a
suitable name mangling (or you'll take whatever I pick;),
but its a pretty simple seach and replace in not too many
files -- so ping me if that will be helpful.

cheers,
Ron

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1424461&group_id=2435