This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: GDB Focus Group at the 2008 GCC Summit
- From: Tom Tromey <tromey at redhat dot com>
- To: Thiago Jung Bauermann <bauerman at br dot ibm dot com>
- Cc: Joel Brobecker <brobecker at adacore dot com>, gdb at sourceware dot org
- Date: Thu, 03 Jul 2008 20:32:54 -0600
- Subject: Re: GDB Focus Group at the 2008 GCC Summit
- References: <20080619190942.GA3744@adacore.com> <m3mylc18tn.fsf@fleche.redhat.com> <1215055590.6789.1.camel@localhost.localdomain> <20080703123426.GA6795@caradoc.them.org>
- Reply-to: Tom Tromey <tromey at redhat dot com>
>>>>> "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