Date: Mon, 07 Dec 2009 14:11:44 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Luigi Rizzo <rizzo@iet.unipi.it> Cc: svn-src-head@freebsd.org, Ed Schouten <ed@80386.nl>, svn-src-all@freebsd.org, src-committers@freebsd.org, Hajimu UMEMOTO <ume@freebsd.org> Subject: Re: the need for safe dynamic string libraries Message-ID: <86skbnrkrz.fsf@ds4.des.no> In-Reply-To: <20091207130433.GA71902@onelab2.iet.unipi.it> (Luigi Rizzo's message of "Mon, 7 Dec 2009 14:04:33 %2B0100") References: <200912052009.nB5K9okL098577@svn.freebsd.org> <ygek4wzpdv3.wl%ume@mahoroba.org> <20091207055752.GD64905@hoeg.nl> <20091207085927.GC57764@onelab2.iet.unipi.it> <86iqcjt93c.fsf@ds4.des.no> <20091207105343.GA62012@onelab2.iet.unipi.it> <86ein7t5m5.fsf@ds4.des.no> <20091207130433.GA71902@onelab2.iet.unipi.it>
next in thread | previous in thread | raw e-mail | index | archive | help
Luigi Rizzo <rizzo@iet.unipi.it> writes: > "Dag-Erling Sm=C3=B8rgrav" <des@des.no> writes: > > When libsbuf was ported to userland, sbuf_printf() was pessimized > > due to the limitations of libc's printf(). > but, isn't this an implementation detail ? What prevents the same > API to have two different implementation, one for kernel, one for userlan= d ? Maybe I wasn't entirely clear: functionality was removed from libsbuf because it could not be implemented in userland, because our printf(3) is badly implemented. To restore that functionality, we would have to either fork libsbuf or fix printf(3). DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86skbnrkrz.fsf>