From owner-freebsd-current@FreeBSD.ORG  Sat Dec 17 11:05:17 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 48E0016A41F
	for <current@freebsd.org>; Sat, 17 Dec 2005 11:05:17 +0000 (GMT)
	(envelope-from rizzo@icir.org)
Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68])
	by mx1.FreeBSD.org (Postfix) with ESMTP id AA6F943D53
	for <current@freebsd.org>; Sat, 17 Dec 2005 11:05:16 +0000 (GMT)
	(envelope-from rizzo@icir.org)
Received: from xorpc.icir.org (localhost [127.0.0.1])
	by xorpc.icir.org (8.12.11/8.12.11) with ESMTP id jBHB5ECC082607;
	Sat, 17 Dec 2005 03:05:14 -0800 (PST)
	(envelope-from rizzo@xorpc.icir.org)
Received: (from rizzo@localhost)
	by xorpc.icir.org (8.12.11/8.12.3/Submit) id jBHB5DdN082606;
	Sat, 17 Dec 2005 03:05:13 -0800 (PST) (envelope-from rizzo)
Date: Sat, 17 Dec 2005 03:05:13 -0800
From: Luigi Rizzo <rizzo@icir.org>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Message-ID: <20051217030513.A82342@xorpc.icir.org>
References: <20051217102835.GC33190@uk.tiscali.com>
	<23883.1134815699@critter.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <23883.1134815699@critter.freebsd.dk>;
	from phk@phk.freebsd.dk on Sat, Dec 17, 2005 at 11:34:59AM +0100
Cc: current@freebsd.org, Brian Candler <B.Candler@pobox.com>
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 11:05:17 -0000

On Sat, Dec 17, 2005 at 11:34:59AM +0100, Poul-Henning Kamp wrote:
> 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.

phk, i don't understand your objection.
aren't (or shouldn't) all of these written as wrappers
for a generic ext_*printf() ?

or your objection is not on the number of different interfaces to
the same thing, but rather the fact that by calling it printf you
can use the existing GLIBC glue to register extensions etc ?

I love the idea of extensible printf, and it's way way useful
when handling ip addresses, hexdump and whatnot; but
portability is an issue, and nobody would use it if
the source code doesn't port to other systems.

cheers
luigi