Re: cb/pedantic-build-for-developers, POSIX-but-not-C99 and -Wno-pedantic-ms-format

René Scharfe [off-list ref] writes:

The lack of warnings about the use of that extension in po/ means
translated formats are not checked by the compiler at all, right?
According to the gettext documentation [2] msgfmt takes care of that
when building the translation files, though.

It is not even seen by the compiler at compilation time, right?  _()
at runtime is merely a function call to map its parameter string to
another string using what is in .mo (compiled from po/).

Am 22.09.21 um 18:15 schrieb Junio C Hamano:

René Scharfe [off-list ref] writes:

quoted

The lack of warnings about the use of that extension in po/ means
translated formats are not checked by the compiler at all, right?
According to the gettext documentation [2] msgfmt takes care of that
when building the translation files, though.

It is not even seen by the compiler at compilation time, right?  _()
at runtime is merely a function call to map its parameter string to
another string using what is in .mo (compiled from po/).

Right, and it's up to the program that builds these .mo files (msgfmt)
to only accept valid mappings between printf format strings.

René