> From: openocd-development-boun...@lists.berlios.de [mailto:openocd- > development-boun...@lists.berlios.de] On Behalf Of David Brownell > Sent: dinsdag 29 september 2009 20:44 > To: simon qian > Cc: openocd-development@lists.berlios.de > Subject: Re: [Openocd-development] OUT macro redefined under MinGW > > On Tuesday 29 September 2009, simon qian wrote: > > OUTPUT doesn't conflict with system header files. > > I checked in a fix. > > > > But I recommend to use MODULE_XXXXX to define a macro, > > so it will never conflict with anything. > > After all, IN, OUT, OUTPUT, INPUT and COUNTER are > > commonly used. > > The real bug here is that the MinGW system headers > (or is it Win32?) chose to pollute global namespaces. > > Yeah, I know it's unrealistic to expect standard > coding discipline from the Win32 system headers. But > it's fair to point out the root causes of bugs. ;)
OT: In that case the creators of Xfree / tinyx also deserve a kick in the nuts for defining index in the include files. Now I really know how many applications have a variable name called 'index'. Nico Coesel _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
