From: David Carlton <carlton@math.stanford.edu>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com, ezannoni@redhat.com
Subject: Re: [rfa] linespec.c, part 5
Date: Sat, 16 Nov 2002 10:53:00 -0000 [thread overview]
Message-ID: <ro1el9l5ou6.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <2950-Sat16Nov2002114552+0200-eliz@is.elta.co.il>
On Sat, 16 Nov 2002 11:45:53 +0300, "Eli Zaretskii" <eliz@is.elta.co.il> said:
>> From: David Carlton <carlton@math.stanford.edu>
>> Date: 15 Nov 2002 14:25:38 -0800
>> * While preparing this patch, I noticed that the variable
>> gdb_completer_quote_characters is declared but not used; I got rid
>> of it.
> While making all these changes, you do make sure that completion on
> the names of functions, variables, classes, etc. still works, right?
> (That completion includes the correct handling of quoted names,
> btw.)
I've been running it through the testsuite, but I have no particular
reason to believe that the testsuite comprehensively tests everything
that decode_line_1 does. There are some completion tests in
gdb.base/completion.exp, so at least some of the completion has been
tested.
It would probably be a boon to GDB for somebody to ensure that the
testsuite comprehensively tests decode_line_1.
By the way, if you were worried about the removal of
gdb_completer_quote_characters, it was replaced by an accessor
function get_gdb_completer_quote_characters a couple of years ago.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2002-11-16 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 14:25 David Carlton
2002-11-15 17:15 ` Elena Zannoni
2002-11-16 11:16 ` David Carlton
2002-12-05 9:16 ` Elena Zannoni
2002-12-05 14:03 ` David Carlton
2002-11-16 1:46 ` Eli Zaretskii
2002-11-16 10:53 ` David Carlton [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-15 14:18 David Carlton
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=ro1el9l5ou6.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=eliz@is.elta.co.il \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.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