Eric Blake <e...@byu.net> writes:
> According to Simon Josefsson on 1/22/2009 3:29 AM:
>> +
>> +void
>> +emit_bug_reporting_address (void)
>> +{
>> + /* TRANSLATORS: The placeholder indicates the bug-reporting address
>> + for this package. Please add _another line_ saying
>> + "Report translation bugs to <...>\n" with the address for translation
>> + bugs (typically your translation team's web or email address). */
>> + printf (_("\nReport bugs to <%s>.\n"), PACKAGE_BUGREPORT);
>> + printf (_("%s home page: http://www.gnu.org/software/%s/\n";),
>> + PACKAGE_NAME, PACKAGE);
>> + printf (_("General help using GNU software:
>> http://www.gnu.org/gethelp/\n";));
>
> In m4, I was using xprintf instead of printf. Is it worth the extra
> security here? printf can fail for reasons like ENOMEM which do not set
> the ferror flag and thus are not caught by the close_stdout atexit module,
> so a robust program should be checking for failures.
Does this problem occur in practice on any modern platform?
Using fprintf, to support other output streams, occurred to me, though.
/Simon
