Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dan@www.cgsoftware.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] Improve completion of locations
Date: Sun, 06 May 2001 00:10:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0105060304320.8302-100000@www.cgsoftware.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1010506091647.4974F-100000@is>

>
> I actually tested this, and it seemed to work, but perhaps I didn't
> test enough.  Could you please post a test program where this should
> be an issue?  I'm afraid my C++ talents are virtually non-existent.

I can make it fail miserably with a simple example (IE my first
try).

Try the following:
#include <stdio.h>
class fred
{
	public:
		int bob();
};
int fred::bob()
{
	return 5;
}
int main(void)
{
	fred test;
	test.bob();
}


Complete on 'fred
It'll list fred and fred::bob(void)

Hit enter (you need to clear the completion status to make it redo the
list)

Complete on 'fred:

It'll list every symbol around (Or at least, 3792 of them, i would
imagine this is every single one, i never checked)

Complete on 'fred::
It'll complete to fred::bob(void)

The first is fine
The third is fine
The second is what your patch breaks right now.

It'll also break completion without quotes when i get around to rewriting
those amazingly complex parsing routines.

Would anyone really object if i just started a flex based lexer to parse
the specs, to replace all this silly ad-hoc parsing.
It seems pretty easy to do using the state based stuff in flex.
(It makes more sense to do it that way for our purposes, than using
lex+yacc.)

>
> And thanks for reviewing the patch.
>


  reply	other threads:[~2001-05-06  0:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-05 10:59 Eli Zaretskii
2001-05-05 11:26 ` Daniel Berlin
2001-05-05 23:15   ` Eli Zaretskii
2001-05-06  0:10     ` Daniel Berlin [this message]
2001-05-06  2:05       ` Eli Zaretskii
2001-05-06  9:38         ` Daniel Berlin
2001-05-06 10:04           ` Eli Zaretskii
2001-05-06  3:19       ` Eli Zaretskii
2001-05-08 13:32 ` Elena Zannoni
2001-05-09  3:46   ` Eli Zaretskii
2001-05-11 21:17     ` Elena Zannoni
2001-05-11 23:03       ` Eli Zaretskii
2001-05-14 13:39         ` Elena Zannoni
2001-05-25  1:39   ` Eli Zaretskii
2001-06-04 23:15 ` Eli Zaretskii
2001-06-05  6:10   ` Fernando Nasser
2001-06-05 10:58     ` Eli Zaretskii
2001-06-10  8:46 ` Fernando Nasser
2001-06-10  9:14   ` Daniel Berlin
2001-06-10  9:43     ` Fernando Nasser
2001-06-11  9:09   ` Eli Zaretskii

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=Pine.LNX.4.33.0105060304320.8302-100000@www.cgsoftware.com \
    --to=dan@www.cgsoftware.com \
    --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