Date: Thu, 4 Dec 2008 18:13:10 -0500 (EST) From: Garrett Wollman <wollman@hergotha.csail.mit.edu> To: peter@wemm.org Cc: arch@freebsd.org Subject: Re: Adding strndup(3) to libc viable/useful? Message-ID: <200812042313.mB4NDA6j045334@hergotha.csail.mit.edu> In-Reply-To: <e7db6d980812041127t6109ebbcr8a68822bdd91cc92@mail.gmail.com> References: <49381DD4.2000506@kasimir.com> <49382502.1040403@delphij.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <e7db6d980812041127t6109ebbcr8a68822bdd91cc92@mail.gmail.com>, Peter Wemm writes: >glibc has had this for a long time and the trend for this function >seems to be gaining ground. I think solaris is the last remaining >major holdout. Many formerly glibc-only functions have been adopted in the current (IEEE Std.1003.1-2008, ISO/IEC 9945:2009) POSIX revision. >FWIW, there are a bunch of other useful utility str*() and mem*() >functions that glibc has that we do not. Any of the functions that POSIX has adopted should definitely be added. >I've run into the lack of fmemopen() in the past. I found an >implementation from rwatson. fmemopen() is one of them. -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200812042313.mB4NDA6j045334>