Subject: Re: syslog_r (Re: CVS commit: src/lib/libc)
To: Christos Zoulas <email@example.com>
From: Jason Thorpe <firstname.lastname@example.org>
Date: 10/26/2006 09:31:26
On Oct 26, 2006, at 6:57 AM, 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.
Because the current syslog_r(3) API / ABI might not be what we settle
Checking this code in was quite premature. What was driving it?