From owner-cvs-all@FreeBSD.ORG Wed Jan 25 19:18:37 2006 Return-Path: X-Original-To: cvs-all@freebsd.org Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE22916A41F; Wed, 25 Jan 2006 19:18:37 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60FD743D69; Wed, 25 Jan 2006 19:18:37 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.17.229]) ([10.251.17.229]) by a50.ironport.com with ESMTP; 25 Jan 2006 11:18:35 -0800 Message-ID: <43D7CF0C.3040607@elischer.org> Date: Wed, 25 Jan 2006 11:18:36 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <19618.1138216547@critter.freebsd.dk> In-Reply-To: <19618.1138216547@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/include printf.h src/lib/libc/stdio Makefile.inc xprintf.c xprintf_errno.c xprintf_quote.c xprintf_vis.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2006 19:18:38 -0000 Poul-Henning Kamp wrote: >In message <43D7C838.4000202@elischer.org>, Julian Elischer writes: > > >>Poul-Henning Kamp wrote: >> >> > > > >>> FreeBSD src repository >>> >>> Modified files: >>> include printf.h >>> lib/libc/stdio Makefile.inc xprintf.c xprintf_vis.c >>> Added files: >>> lib/libc/stdio xprintf_errno.c xprintf_quote.c >>> Log: >>> Make the %V{is} extension handle a NULL pointer like %s does: output "(null)" >>> >>> Add %M{essage} extension which prints an errno value as the >>> corresponding string if possible or numerically otherwise. >>> >>> >>Is this compatible with anyone else? >> >> > >Not that I know off. It is an optional extension which you have to >ask for explicitly, so it is non-intrusive as far as stadnards go. > > > >>basically, did this idea come from somewhere? or is it new? >> >> > >Extending printf is as old as at least SYSIII. > >The specific implementation was written to be compatible with GLIBC. > > do you mean "not collide with" or "emulate" glibc?