Follow-up Comment #4, bug #43970 (project gettext):
I see, this didn't occur to me (nor the fact that C++11 compiler won't compile
this until now). Wouldn't it be better, then, to (if necessary) start making a
distinction between C and C++ modes, instead of introducing a new C++11 one?
IMHO the example you gave is quite artificial and very unlikely to occur in
practice, but I get your point. It is even less likely to occur in C++,
though, because of the C++ culture that really frowns upon such macro uses.
Plus C++ compilers will eventually switch to having C++11/4/7 as the default
(some already did, although not gcc) and such code would have to be updated
anyway, making the chance of it occurring ever smaller.
The advantage of that would be that xgettext already differentiates between C
and C++ in its user interface (although not in the implementation, I think).
And it wouldn't be something that would have to be reevaluated in a few years
once legacy C++98 becomes, well, legacy for real.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?43970>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
