Peter Wemm 15aa00d597 Add an implementation of the gnu-ish asprintf() and vasprintf(). They are ... not based on gpl'ed code, just prototype and usage. I'm not 100% certain they behave the same while the system is in trouble (eg: malloc() failing) but in those circumstances all bets would be off anyway. These routines work like sprintf() and vsprintf(), except that instead of using a fixed buffer, they allocate memory and return it to the user and it's the user's responsibility to free() it. They have allocate as much memory as they need (and can get), so the size of strings it can deal with is limited only by the amount of memory it can malloc() on your behalf. There are a few gpl'ed programs starting to use this interface, and it's becoming more common with the scares about security risks with sprintf(). I dont like the look of the code that the various programs (including cvs, gdb, libg++, etc) provide if configure can't find it on the system. It should be possible to modify the stdio core code to provide this interface more efficiently, I was more worried about having something that worked and was secure. :-) (I noticed that there was once intended to be a smprintf() routine when our stdio was written for 4.4BSD, but it looks pretty stillborn, and it's intended interface is not clear). Since Linux and gnu libc have this interface, it seemed silly to bring yet another one onto the scene.		1996-05-27 10:49:43 +00:00
..
csu/i386
libc
libc_r
libcom_err
libcompat
libcrypt
libcurses
libdisk
libedit
libf2c
libF77
libfakegnumalloc
libforms
libgnumalloc
libI77
libipx
libkse
libkvm
libm
libmd
libmytinfo
libncurses
libpam/modules
libpcap
libpthread
libresolv
librpcsvc
libscsi
libskey
libss
libtelnet
libtermcap
libutil
libxpg4
liby
msun
ncurses/ncurses
Makefile
Makefile.inc