From owner-freebsd-bugs Thu Jan 6 23:10:11 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A1200155D9 for ; Thu, 6 Jan 2000 23:10:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id XAA82425; Thu, 6 Jan 2000 23:10:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Thu, 6 Jan 2000 23:10:02 -0800 (PST) Message-Id: <200001070710.XAA82425@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: bin/15929: printf(1) truncates if it sees 000 Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/15929; it has been noted by GNATS. From: Sheldon Hearn To: Archie Cobbs Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/15929: printf(1) truncates if it sees 000 Date: Fri, 07 Jan 2000 09:08:33 +0200 On Thu, 06 Jan 2000 09:33:49 PST, Archie Cobbs wrote: > 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? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message