From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28213 invoked by alias); 15 Sep 2007 13:52:38 -0000 Received: (qmail 28201 invoked by uid 22791); 15 Sep 2007 13:52:38 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 15 Sep 2007 13:52:32 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id F3BFE982A2; Sat, 15 Sep 2007 13:52:30 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 9297A98108; Sat, 15 Sep 2007 13:52:30 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.67) (envelope-from ) id 1IWY4T-0004Jg-9W; Sat, 15 Sep 2007 09:52:29 -0400 Date: Sat, 15 Sep 2007 13:52:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: mark.kettenis@xs4all.nl, jan.kratochvil@redhat.com, gdb-patches@sourceware.org Subject: Re: [patch] printf "%p" gdb internal error fix Message-ID: <20070915135229.GA15879@caradoc.them.org> Mail-Followup-To: Eli Zaretskii , mark.kettenis@xs4all.nl, jan.kratochvil@redhat.com, gdb-patches@sourceware.org References: <20060910172037.GA3886@host0.dyn.jankratochvil.net> <200609101931.k8AJVF4m026090@elgar.sibelius.xs4all.nl> <20070904141926.GA27477@caradoc.them.org> <20070904205307.GA17062@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.15 (2007-04-09) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-09/txt/msg00188.txt.bz2 On Sat, Sep 15, 2007 at 11:59:52AM +0300, Eli Zaretskii wrote: > Never liked such references too much, but I guess a full-fledged > description of conversion specifiers will have to wait for another > rainy day. Until then, here's what I committed, in order to bring > the manual in line with the code, and at least tell what features of a > C-standard `printf' are _not_ supported: Thanks! May I suggest we reference a particular C or POSIX standard if we are going to list exceptions? When I wrote the current implementation, I did it with a copy of C89 open next to me (well, I think - I can't find the exact manual I was using) and GCC's format string checker, which is a fairly definitive reference. Of the exceptions you've found, * and n are present in C89. 1$, ', hh, j, t, z, a, and A are not (actually I can't find a reference for a/A; what do they do?). -- Daniel Jacobowitz CodeSourcery