Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pierre-Marie de Rodat <derodat@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [Ada] Fix completion for multiple function matches
Date: Tue, 01 Sep 2015 12:15:00 -0000	[thread overview]
Message-ID: <20150901121528.GB3356@adacore.com> (raw)
In-Reply-To: <55E55526.2000303@adacore.com>

> I adjusted the testcase in the way I think you meant: I added the
> Ambiguous_Prog procedure to Aux_Pck and added a test to ask the completion
> of "p ambig": GDB correctly reports two possible completions: "p
> ambiguous_func" and "p ambiguous_proc". This looks independent of function
> resolution in ada-lang, and that is fortunate in our case. :-)
> 
> Is this what you had in mind?

Yep :)

> gdb/ChangeLog:
> 
> 	* ada-lang.c (ada_resolve_function): Do not ask the user what
> 	match to use when in completion mode.
> 
> gdb/testsuite/ChangeLog:
> 
> 	* gdb.ada/complete.exp: Add "pck.ambiguous_func" to the relevant
> 	expected outputs.  Add two testcases for completing ambiguous
> 	functions.
> 	* gdb.ada/complete/aux_pck.adb: New file.
> 	* gdb.ada/complete/aux_pck.ads: New file.
> 	* gdb.ada/complete/foo.adb: Pull Aux_Pck and call the two
> 	Ambiguous_Func functions.
> 	* gdb.ada/complete/pck.ads: Add an Ambiguous_Func function.
> 	* gdb.ada/complete/pck.adb: Likewise.

Looks good. Go ahead and push :).

Thank you, Pierre-Marie.
-- 
Joel


  reply	other threads:[~2015-09-01 12:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 15:26 Pierre-Marie de Rodat
2015-08-31 17:25 ` Joel Brobecker
2015-09-01  7:35   ` Pierre-Marie de Rodat
2015-09-01 12:15     ` Joel Brobecker [this message]
2015-09-01 12:55       ` Pierre-Marie de Rodat

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=20150901121528.GB3356@adacore.com \
    --to=brobecker@adacore.com \
    --cc=derodat@adacore.com \
    --cc=gdb-patches@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