Subject: Re: syslog_r (Re: CVS commit: src/lib/libc)
To: Christos Zoulas <email@example.com>
From: Thor Lancelot Simon <firstname.lastname@example.org>
Date: 10/26/2006 10:13:09
On Thu, Oct 26, 2006 at 09:57:22AM -0400, Christos Zoulas wrote:
> On Oct 26, 8:23pm, email@example.com (SODA Noriyuki) wrote:
> -- Subject: Re: syslog_r (Re: CVS commit: src/lib/libc)
> | Isn't it better to remove syslog_r() from libc as soon as possible,
> | at least until this issue is settled?
> | Since leaving it in libc may cause an ABI problem.
> Why would it cause an ABI issue? the use of vsnprintf() is internal.
Soda and I are both suggesting that syslog_r() should be removed -- so if
there is code floating around out there in the world that expects it in
libc, then we have an ABI issue.
How do you intend to make syslog_r() safe when it's specified so that it
accepts arbitrary format strings?
Thor Lancelot Simon firstname.lastname@example.org
"We cannot usually in social life pursue a single value or a single moral
aim, untroubled by the need to compromise with others." - H.L.A. Hart