1 Apr 2011 07:12
RE: [RFC 1/9] Unify windows specifics into common/windows-hdep files
Pierre Muller <pierre.muller <at> ics-cnrs.unistra.fr>
2011-04-01 05:12:42 GMT
2011-04-01 05:12:42 GMT
> > From: "Pierre Muller" <pierre.muller <at> ics-cnrs.unistra.fr> > > Cc: <gdb-patches <at> sourceware.org> > > Date: Wed, 30 Mar 2011 23:32:36 +0200 > > > > > > +#undef _G_SUFFIX > > > > > > I think the C Standard says that macros whose name begins with an > > > underscore and a capital letter are reserved. Applications should not > > > use such macros. > > > > But we are also using __USEWIDE before my patch ... > > or do you mean that two underscores are OK? > > No, AFAIK macros that begin with two underscores are also reserved. But nobody protested for __USEWIDE nor for __PMAX for instance... But checking gdb directory, it seems that are only a fee macros starting with an underscore. > > I completely remove __USEWIDE and tried to replace it by this new > > USE_WIDE_WINAPI. > > Or is this __USEWIDE macro used anywhere else than inside GDB code? > > I don't think so, but maybe someone else could tell for sure. > > > Should I rather call the macro USE_UNICODE_WINAPI > > (and USE_ANSI_WINAPI to force ANSI version?) > > I don't think it matters what the macro is called.(Continue reading)
RSS Feed