From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8406 invoked by alias); 19 Nov 2012 21:56:38 -0000 Received: (qmail 8380 invoked by uid 22791); 19 Nov 2012 21:56:37 -0000 X-SWARE-Spam-Status: No, hits=-6.8 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 19 Nov 2012 21:56:25 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qAJLuOjO029696 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 19 Nov 2012 16:56:24 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id qAJLuN3K008278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 19 Nov 2012 16:56:23 -0500 From: Tom Tromey To: Jim Blandy Cc: gdb ml Subject: Re: Fwd: Addresses in pretty-printing References: Date: Mon, 19 Nov 2012 21:56:00 -0000 In-Reply-To: (Jim Blandy's message of "Sun, 18 Nov 2012 23:11:28 -0800") Message-ID: <878v9xp88o.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-11/txt/msg00056.txt.bz2 >>>>> "Jim" == Jim Blandy writes: Jim> Here is proposed documentation for gdb.Value.format, and two Jim> accompanying functions, gdb.value_print_options and Jim> gdb.set_value_print_options. I'd be willing to implement something Jim> like this. It seems like a worthwhile facility to me. I think one possible objection is that this kind of thing will let pretty-printer authors effectively override user settings. However, we've see that they already do this, and it isn't really possible (or perhaps arguably desirable) to stop them. Your proposal makes the resulting code cleaner and is also, I think, useful for writing new commands. Jim> @findex gdb.set_value_print_options Jim> @defun gdb.set_value_print_options (options) Jim> Set the value printing options as given in @var{options}, a dictionary Jim> whose items' keys name value printing options, and whose values are Jim> the values to which those options should be set. Permitted keys are as Jim> for @code{gdb.value_print_options}, described above. This is just shorthand for a bunch of calls to gdb.execute, to set the various parameters? Tom