Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: tromey@redhat.com, Joel Brobecker <brobecker@adacore.com>,
		gdb@sourceware.org
Subject: Re: GDB Focus Group at the 2008 GCC Summit
Date: Thu, 03 Jul 2008 12:35:00 -0000	[thread overview]
Message-ID: <20080703123426.GA6795@caradoc.them.org> (raw)
In-Reply-To: <1215055590.6789.1.camel@localhost.localdomain>

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


  parent reply	other threads:[~2008-07-03 12:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 19:10 Joel Brobecker
2008-06-22  6:08 ` Thiago Jung Bauermann
2008-06-22 11:52 ` Nick Roberts
2008-06-22 13:53   ` Joel Brobecker
2008-06-23 15:17   ` Tom Tromey
2008-06-23 17:35     ` Jim Ingham
2008-06-23 21:55     ` Nick Roberts
2008-06-23 15:16 ` Tom Tromey
2008-06-26  0:24   ` Tom Tromey
2008-07-03  3:27   ` Thiago Jung Bauermann
2008-07-03  8:12     ` Andreas Schwab
2008-07-03 12:35     ` Daniel Jacobowitz [this message]
2008-07-03 14:28       ` Thiago Jung Bauermann
2008-07-04  2:33       ` Tom Tromey
2008-07-04  3:19         ` Daniel Jacobowitz
2008-06-23 21:46 ` Jason Molenda
2008-06-23 22:22   ` Nick Roberts
2008-06-24 21:18     ` Nick Roberts
2008-06-25  6:56       ` [MI] changing breakpoint location (Was: GDB Focus Group at the 2008 GCC Summit) Vladimir Prus
2008-06-23 22:09 ` GDB Focus Group at the 2008 GCC Summit Mark Kettenis
2008-06-23 22:26   ` Joel Brobecker
2008-06-24  8:35   ` Andrew STUBBS
2008-06-24  8:56     ` Andreas Schwab
2008-06-24 18:12     ` Michael Snyder
2008-06-24 18:28     ` Daniel Jacobowitz
2008-06-24 19:33     ` Dave Korn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080703123426.GA6795@caradoc.them.org \
    --to=drow@false.org \
    --cc=bauerman@br.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=tromey@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox