From: Sami Wagiaalla <swagiaal@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: Petr Machata <pmachata@redhat.com>, frysk@sourceware.org
Subject: Re: Shortcomings of HPD '#' identifier qualification syntax
Date: Mon, 28 Apr 2008 11:55:00 -0000 [thread overview]
Message-ID: <48121A43.7000908@redhat.com> (raw)
In-Reply-To: <47FB7039.3000304@redhat.com>
I am now starting to implement # parsing in the search engine.
I would like to generate a list of all possible queries that
the search engine can be asked for.
Here is what I have so far:
- #lib#file#symbol
- #lib#file#symbol@version ?
- #lib#file#plt:symbol ?
- #lib#symbol
- #lib#symbol@version ?
- #lib#plt:symbol ?
- #file#symbol
- #file#line
Any additions, corrections, comments ?
Sami Wagiaalla
prev parent reply other threads:[~2008-04-25 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 2:06 Petr Machata
2008-04-08 13:45 ` Andrew Cagney
2008-04-08 14:56 ` Petr Machata
2008-04-28 11:55 ` Sami Wagiaalla [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=48121A43.7000908@redhat.com \
--to=swagiaal@redhat.com \
--cc=cagney@redhat.com \
--cc=frysk@sourceware.org \
--cc=pmachata@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).