Xref: utzoo comp.lang.c:8901 comp.std.c:2
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!mcnc!rti!xyzzy!meissner
From: meissner@xyzzy.UUCP (Michael Meissner)
Newsgroups: comp.lang.c,comp.std.c
Subject: Re: vsprintf considered dangerous
Message-ID: <744@xyzzy.UUCP>
Date: 5 Apr 88 14:49:13 GMT
References: <36@lotus.UUCP> <1219@ucsfcca.ucsf.edu> <3312@haddock.ISC.COM>
Reply-To: meissner@xyzzy.UUCP (Michael Meissner)
Organization: Data General (Languages @ Research Triangle Park, NC.)
Lines: 11

In article <3312@haddock.ISC.COM> karl@haddock.ima.isc.com (Karl Heuer) writes:
| In article <1219@ucsfcca.ucsf.edu> roland@rtsg.lbl.gov (Roland McGrath) writes:
| >[The GNU C library has snprintf() and vsnprintf()]
| 
| This problem came up some time ago in this newsgroup, and I thought I heard it
| said that X3J11 recognized the need for a "safe" sprintf() and would be adding
| snprintf() to the ANSI library.  Whatever happened to that proposal?

It did not get the necessary 2/3 vote to add it, so the proposal was rejected.
-- 
Michael Meissner, Data General.		Uucp: ...!mcnc!rti!xyzzy!meissner
					Arpa/Csnet:  meissner@dg-rtp.DG.COM