Path: utzoo!attcan!uunet!vsedev!logan
From: logan@vsedev.VSE.COM (James Logan III)
Newsgroups: comp.lang.c
Subject: Re: gets(3) nonsense
Message-ID: <1251@vsedev.VSE.COM>
Date: 23 Nov 88 00:28:44 GMT
References: <867@cernvax.UUCP> <645@quintus.UUCP> <339@igor.Rational.COM> <14447@mimsy.UUCP> <1643@solo11.cs.vu.nl> <1403@unisoft.UUCP> <644@scotty.UUCP>
Reply-To: logan@vsedev.VSE.COM (James Logan III)
Organization: VSE Software Development Lab
Lines: 20

In article <644@scotty.UUCP> jwr@scotty.UUCP (Dier Retlaw Semaj) writes:
>
>What about sprintf() & fprintf()?
>The user does not have *complete control* over these functions.

True, sprintf() could write beyond the end of the string passed
as its first parameter.  But I don't see what damage fprintf()
would do, unless it does not check its internal buffer boundaries
as it expands the format string.  If that's the problem then
printf() would have the same problem.  Anyone here seen the
source?   

Hey, lets do away with printf! :-)

			-Jim

-- 
Jim Logan		logan@vsedev.vse.com
(703) 892-0002		uucp:	..!uunet!vsedev!logan
			inet:	logan%vsedev.vse.com@uunet.uu.net