Subject: Re: syslog_r (Re: CVS commit: src/lib/libc)
To: SODA Noriyuki <firstname.lastname@example.org>
From: Christos Zoulas <email@example.com>
Date: 10/27/2006 13:33:45
On Oct 28, 2:24am, firstname.lastname@example.org (SODA Noriyuki) wrote:
-- Subject: Re: syslog_r (Re: CVS commit: src/lib/libc)
| >>>>> On Thu, 26 Oct 2006 19:18:12 +0000 (UTC),
| email@example.com (Christos Zoulas) said:
| > Finally we provide a snprintf_r() and a vsnprintf_r() [call them what you
| > wish] wrappers that look like the nor _r functions, but they only do:
| Using the "_r" suffix for async-signal-safe functions is a bad idea,
| because other "_r" functions are not async-signal-safe, but merely
| multithread-safe, and our snprintf() and vsnprintf() are already
| If we'd like to provide an async-signal-safe variant of function,
| we should use a suffix other than "_r".
There is no precedence for that that I know of. How about "_a"?