From owner-freebsd-current@FreeBSD.ORG Sat Dec 17 11:30:34 2005 Return-Path: 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 4E11F16A422 for ; Sat, 17 Dec 2005 11:30:34 +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 93FBC43D45 for ; Sat, 17 Dec 2005 11:30:31 +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 52D50BC66; Sat, 17 Dec 2005 11:30:29 +0000 (UTC) To: Luigi Rizzo From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 17 Dec 2005 03:27:06 PST." <20051217032706.A82898@xorpc.icir.org> Date: Sat, 17 Dec 2005 12:30:28 +0100 Message-ID: <24152.1134819028@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: current@freebsd.org, Brian Candler 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 11:30:34 -0000 In message <20051217032706.A82898@xorpc.icir.org>, Luigi Rizzo writes: >On Sat, Dec 17, 2005 at 12:18:11PM +0100, Poul-Henning Kamp wrote: >> In message <20051217030513.A82342@xorpc.icir.org>, Luigi Rizzo writes: >... >> >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. >> >> Everything under the sun has a portability cost these days because >> the portable subset of the UNIX API is still too small to support >> sensible programming. >... >> For an extensible printf, I see little reason to add yet another >> API, the GLIBC people got here first, the API is not optimal, but >> it does work. > >so let me understand - perhaps i am missing this point. > >are you saying that if you link a program that uses these extensions >with glibc it behaves as expected ? Then the portability issue >would disappear (i.e. moves elsewhere where hopefully it has been >solved already). I'd really hope so, but havn't tried. -- 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.