Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb@sourceware.org
Subject: Re: GDB Focus Group at the 2008 GCC Summit
Date: Fri, 04 Jul 2008 02:33:00 -0000	[thread overview]
Message-ID: <m3d4lujs4p.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20080703123426.GA6795@caradoc.them.org> (Daniel Jacobowitz's message of "Thu\, 3 Jul 2008 08\:34\:26 -0400")

>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:

Daniel> Here's a suggestion: $builtin, like the bash 'builtin' builtin (can't
Daniel> believe I just wrote that sentence).  That would let us recover any
Daniel> lost functions.  Well, they aren't really built-in, so maybe some
Daniel> other name.  The idea of having two names for each, one more
Daniel> convenient and the other more robust.  WDYT?

This is fine except for 'set $builtin = 0'.  I am not really concerned
about it though.

Actually it would be fine by me to install things as both
$gdb_whatever and $whatever by default, not worry if users overwrite
$whatever, and try to have scripts always use the namespaced form.

The current code installs the documentation under "help function name".
But if the user does "set $other = $name; help function other", he
won't get anything sensible.  Perhaps 'help' needs a special case; but
then command completion needs a special case too.

Tom


  parent reply	other threads:[~2008-07-04  2:33 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
2008-07-03 14:28       ` Thiago Jung Bauermann
2008-07-04  2:33       ` Tom Tromey [this message]
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=m3d4lujs4p.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=bauerman@br.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    /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