Re: yesno module consumes too much input

[Eric Blake-1]

> The yesno module has a problem on platforms where exit()
> does not implicitly flush seekable input streams

The yesno module also has a potential POSIX-compliance problem
on all platforms.  Inside rpmatch, the code uses _("^[yY]") to
get the locale-specific regex to use as the yesexpr.  However,
this is not necessarily the same as using nl_langinfo(YESEXPR).
Likewise for NOEXPR.

Either gettext should special-case the strings "^[yY]" and "^[nN]",
or rpmatch should be fixed to use nl_langinfo instead of gettext.

If nothing else, we should add a TRANSLATOR comment before
both regex strings in rpmatch.c, to make it obvious that these strings
should be consistent with the locale's choice of yesexpr and noexpr,
rather than the usual use of _() to designate translated output.

-- 
Eric Blake

-- 
View this message in context: 
http://www.nabble.com/yesno-module-consumes-too-much-input-tf4287835.html#a12206584
Sent from the Gnulib mailing list archive at Nabble.com.