[bug #65053] spurious "hexadecimal escape sequence out of range" warnings

[Vaclav Slavik]

Follow-up Comment #2, bug#65053 (group gettext):

Honestly, both my personal choices I would make when writing new UNIX software
or GNU's guidelines for their software are a bit off-topic to the issue. And
while I appreciate the non-trivialities of working with wchar_t, calling _any_
use of it not portable is a bit of a stretch (case in point, this sample code
is perfectly fine and doesn't hit any of the pain points mentioned in gnulib
docs).

The important part, IMHO, is that wchar_t is part of ISO C++ as well as modern
C standards and so are widechar literals (regardless of one's opinion on their
merit or appropriate use). And as it is, xgettext currently

1. emits warning on perfectly legal, standard-comformant C++ code
2. emits untruthful warning, claiming that the value is out of range even when
it isn't

Moreover, it emits them even for literals that aren't used in i18n functions,
and there's no way to silence the warning, so one has to change even
i18n-unrelated code to accomodate xgettext.

For now at least, there's a workaround that I didn't think about myself;
another person alerted me to it: use \u instead of \x.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?65053>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/