Adding strndup(3) to libc viable/useful?

[Xin LI]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Garrett Wollman wrote:
> In article <e7db6d980812041127t6109ebbcr8a68822bdd91cc92 at 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.

Is there a public available version on the Internet?  Google turns out
only an approval notice on Austin group...

>> 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
> 
> _______________________________________________
> freebsd-arch at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-arch
> To unsubscribe, send any mail to "freebsd-arch-unsubscribe at freebsd.org"


- --
Xin LI <delphij at delphij.net>	http://www.delphij.net/
FreeBSD - The Power to Serve!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkk67r0ACgkQi+vbBBjt66CNxQCfVT7AqvP5wzYcZ11HS1icuDno
XBYAnj4l/AGiuxUf+PhzRaH3Skt9XEzc
=n9ZK
-----END PGP SIGNATURE-----