From owner-freebsd-current@FreeBSD.ORG  Sat Dec 17 10:35:04 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 366E416A41F
	for <current@freebsd.org>; Sat, 17 Dec 2005 10:35:04 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CCA0043D58
	for <current@freebsd.org>; Sat, 17 Dec 2005 10:35:03 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (unknown [192.168.48.2])
	by phk.freebsd.dk (Postfix) with ESMTP id 8D23FBC66;
	Sat, 17 Dec 2005 10:35:00 +0000 (UTC)
To: Brian Candler <B.Candler@pobox.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Sat, 17 Dec 2005 10:28:35 GMT."
	<20051217102835.GC33190@uk.tiscali.com> 
Date: Sat, 17 Dec 2005 11:34:59 +0100
Message-ID: <23883.1134815699@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
Cc: current@freebsd.org
Subject: Re: About extensible prinf(3), a slightly long X-mas card 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Dec 2005 10:35:04 -0000

In message <20051217102835.GC33190@uk.tiscali.com>, Brian Candler writes:

>Perhaps the semantics of this extended printf() are so far divorced from the
>standard one that you might as well just call it something else? e.g.
>
>    ext_printf()

the reasons not to are

	ext_printf()
	ext_fprintf()
	ext_sprintf()
	ext_snprintf()
	ext_asprintf()
	ext_vprintf()
	ext_vfprintf()
	ext_vsfprintf()
	ext_vasfprintf()

There is little or no point in replicating all of this stuff.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.