From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1281 invoked by alias); 13 Jun 2002 23:36:02 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 1274 invoked from network); 13 Jun 2002 23:36:01 -0000 Received: from unknown (HELO zwingli.cygnus.com) (208.245.165.35) by sources.redhat.com with SMTP; 13 Jun 2002 23:36:01 -0000 Received: by zwingli.cygnus.com (Postfix, from userid 442) id 0BDAA5EA11; Thu, 13 Jun 2002 18:35:59 -0500 (EST) To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com Subject: Re: RFA: Switch TYPE_CODE_METHOD to store arguments like TYPE_CODE_FUNCTION References: <20020604024456.GA8733@branoic.them.org> From: Jim Blandy Date: Thu, 13 Jun 2002 16:36:00 -0000 In-Reply-To: <20020604024456.GA8733@branoic.them.org> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-06/txt/msg00235.txt.bz2 Minor observation: In gdbtypes.h, your patch makes the following change to `struct field': /* Name of field, value or argument. - NULL for range bounds and array domains. */ + NULL for range bounds, array domains, and member function + arguments. */ char *name; Is there any reason this *must* be null? Aren't there times where we do know a method's arguments' names, and where we could fill this in? I guess I'm thinking about the way prototyped function types in C may or may not include the names: typedef int (*foo_t) (int x, int y); typedef int (*bar_t) (int, int); typedef int (*baz_t) (int x, int); Is there any analog to this in C++?