From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: neil@daikokuya.demon.co.uk
Cc: jimb@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: RFA: add macro commands
Date: Sat, 11 May 2002 00:16:00 -0000 [thread overview]
Message-ID: <8361-Sat11May2002101520+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <20020510230813.GA30884@daikokuya.demon.co.uk> (message from Neil Booth on Sat, 11 May 2002 00:08:13 +0100)
> Date: Sat, 11 May 2002 00:08:13 +0100
> From: Neil Booth <neil@daikokuya.demon.co.uk>
>
> Jim Blandy wrote:-
>
> > Given that the macros are stored in a splay tree, they're all sorted
> > in a way that would make efficient completion straightforward. So it
> > wouldn't be too hard to write a macro-only completion function.
>
> Just in case you'd not realized, macro expansions are frequently
> different, depending on location in the source files.
I'm not sure I understand what you mean. I was talking about
completing on macro _names_, not trhe results of their _expansion_.
That is, if I type "print regnum < NUM_" and hit TAB, I'd expect to
see NUM_REGS and NUM_PSEUDO_REGS as possible completions. But I
don't care about the values these two expand to.
So this kind of completion does not depend on the location in the
source files, only on the macros recorded in the debug info.
Am I missing something?
next prev parent reply other threads:[~2002-05-11 7:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 16:58 Jim Blandy
2002-05-09 17:13 ` Daniel Jacobowitz
2002-05-09 20:43 ` Jim Blandy
2002-05-09 17:54 ` Andrew Cagney
2002-05-09 20:43 ` Jim Blandy
2002-05-10 0:16 ` Eli Zaretskii
2002-05-10 8:55 ` Jim Blandy
2002-05-10 9:33 ` Eli Zaretskii
2002-05-10 16:07 ` Neil Booth
2002-05-11 0:16 ` Eli Zaretskii [this message]
2002-05-11 3:45 ` Neil Booth
2002-05-11 13:06 ` Jim Blandy
2002-05-16 14:17 ` Jim Blandy
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=8361-Sat11May2002101520+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=neil@daikokuya.demon.co.uk \
/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