From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8965 invoked by alias); 3 Jul 2008 12:35:35 -0000 Received: (qmail 8690 invoked by uid 22791); 3 Jul 2008 12:35:30 -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; Thu, 03 Jul 2008 12:34:29 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 86DB998373; Thu, 3 Jul 2008 12:34:27 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 47B0A982C3; Thu, 3 Jul 2008 12:34:27 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1KEO14-0001qf-F3; Thu, 03 Jul 2008 08:34:26 -0400 Date: Thu, 03 Jul 2008 12:35:00 -0000 From: Daniel Jacobowitz To: Thiago Jung Bauermann Cc: tromey@redhat.com, Joel Brobecker , gdb@sourceware.org Subject: Re: GDB Focus Group at the 2008 GCC Summit Message-ID: <20080703123426.GA6795@caradoc.them.org> Mail-Followup-To: Thiago Jung Bauermann , tromey@redhat.com, Joel Brobecker , gdb@sourceware.org References: <20080619190942.GA3744@adacore.com> <1215055590.6789.1.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1215055590.6789.1.camel@localhost.localdomain> User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes 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: 2008-07/txt/msg00023.txt.bz2 On Thu, Jul 03, 2008 at 12:26:30AM -0300, Thiago Jung Bauermann wrote: > On Mon, 2008-06-23 at 09:15 -0600, Tom Tromey wrote: > > Our consensus was to use the function-like syntax (second example > > above) and to parse the arguments as expressions. This does mean > > there is a namespace issue, but we reasoned that we could make all the > > standard functions have a "gdb_" prefix or something like that. > > What about using a different symbol, such as '%' instead of the '$' used > for convenience variables? I'd like them to be convenience variables (which is what Tom has implemented). Putting them in the same namespace is a well-established tradition and is how Python behaves - plus it lets them behave transparently like inferior function pointers, which can also be assigned to convenience variables. Here's a suggestion: $builtin, like the bash 'builtin' builtin (can't believe I just wrote that sentence). That would let us recover any lost functions. Well, they aren't really built-in, so maybe some other name. The idea of having two names for each, one more convenient and the other more robust. WDYT? -- Daniel Jacobowitz CodeSourcery