Date: Fri, 7 Jan 2000 11:30:02 -0800 (PST) From: Archie Cobbs <archie@whistle.com> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/15929: printf(1) truncates if it sees 000 Message-ID: <200001071930.LAA10787@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/15929; it has been noted by GNATS. From: Archie Cobbs <archie@whistle.com> To: sheldonh@uunet.co.za (Sheldon Hearn) Cc: FreeBSD-gnats-submit@freebsd.org, bde@whistle.com Subject: Re: bin/15929: printf(1) truncates if it sees 000 Date: Fri, 7 Jan 2000 11:28:27 -0800 (PST) Sheldon Hearn writes: > > But that's not the point, of course. Either the bug should be fixed > > or else at least declared 'normal' and so documented in the man page. > > That's the bit I'm after. What's the bug? From printf(3): > > These functions return the number of characters printed (not including > the trailing `\0' used to end output to strings). > > Presumably, you want some indication in the printf(1) manual page that a > null character in the string terminates it? Or is there something else > you think we can do? Yes, that would be good enough. All I'm saying is that the behavior doesn't match what the man page says. If you forget printf(3), POSIX, etc. and just read the man page, there's nothing in it that says that \000 is in any way special, yet in functionality it is. A simple note in the BUGS section (or wherever) would be just fine with me. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001071930.LAA10787>