From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Enhance completer for fields of structures.
Date: Mon, 22 Apr 2002 04:16:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20020422125444.01c40a60@ics.u-strasbg.fr> (raw)
In-Reply-To: <Pine.SUN.3.91.1020422145208.14580K-100000@is>
At 13:53 22/04/2002 , Eli Zaretskii a écrit:
>On Mon, 22 Apr 2002, Pierre Muller wrote:
>
> > The patch attached below does allow me to get a
> > correct completion of expressions like
> > if X is a variable of type
> > PRECORD, PRECORD being a pointer to type
> > TRECORD = record
> > x,y : longint;
> > next : precord;
> > end;
> >
> > (gdb) print X^.N
> > if I press tab, I get X^.NEXT
> > even if there are several global variables starting with letter N.
>
>Sounds good, but please make sure the change doesn't break any past
>behavior. For example, did you test it with C++ foo:bar and foo::bar
>class members?
No, my C++ knowledge is much too small for this :(
I wouldn't probably be able to find any troubles,
what simple C++ sources could I use to test this out?
What is the difference between one and two ':' in your above example?
Anyhow, for the moment, only the pascal parser does
return a non NULL value for parse_for_type function
so ithe onyl point where a problem could arise is the
supplementary call to make_symbol_completion_list
at start of location_completer.
Maybe it would be safer to call a special version (to be written)
that would only return something if parser_for_type returns a non zero value.
Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99
prev parent reply other threads:[~2002-04-22 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 2:03 Pierre Muller
2002-04-22 3:54 ` Eli Zaretskii
2002-04-22 4:16 ` Pierre Muller [this message]
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=4.2.0.58.20020422125444.01c40a60@ics.u-strasbg.fr \
--to=muller@cerbere.u-strasbg.fr \
--cc=eliz@is.elta.co.il \
--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