[comp.std.c] vsprintf considered dangerous

karl@haddock.ISC.COM (Karl Heuer) (04/05/88)

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?

Karl W. Z. Heuer (ima!haddock!karl or karl@haddock.isc.com), The Walking Lint
(Note: comp.std.c is no longer moderated)

meissner@xyzzy.UUCP (Michael Meissner) (04/05/88)

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