From: Thomas Stroesslin <thomas.stroesslin@epfl.ch>
To: sourcenav@sources.redhat.com
Subject: Re: Xref and find declaration of variables
Date: Thu, 03 May 2001 00:15:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.21.0105030857210.28809-100000@mantrasun3.epfl.ch> (raw)
In-Reply-To: <3AF05198.CBB5E88C@redhat.com>
> > ok, I reformulate the question :-) "do you plan to fix the bug of not
> > having proper scoping?" don't say it's not a bug.....
>
> Heheh, I don't see how it could be a bug.
Ok, you're right.
in the example I mentionned, the Xref should at least say: "I don't
know". However, it pretends knowing what it does and gives me the wrong
answer. This is a bug. Saying that it didn't know would be a missing
feature, which I could accept. I see that probably you'd have to remove
the Xref completely to prevent giving false answers.
> I'll put it another way for you "do you plan to implement a complete
> scoping system?"
>
> The answer is "at some point, when we have time".
>
> Note that what you are asking us to do doesn't exist
> in SN yet. Maybe some hack or work around could be used,
I didn't know there was little (or none at all?) scoping support. I only
guessed :-)
Note: I would not dare asking you to implement it. I rather ask
_if_ you planned to implement it, and heck, this is not the same
The essence of my postings:
Having a good xref is the most important thing for me. I don't care much
about other features, I just want a good xref, and I want you to know
that.
thanks,
tom
next prev parent reply other threads:[~2001-05-03 0:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 9:10 Thomas Stroesslin
2001-05-01 10:32 ` Richard F Weber
2001-05-02 4:33 ` Thomas Stroesslin
2001-05-02 11:28 ` Ian Roxborough
2001-05-03 0:15 ` Thomas Stroesslin [this message]
2001-05-02 12:43 ` Mo DeJong
2001-05-01 10:52 ` Mo DeJong
-- strict thread matches above, loose matches on Subject: below --
2001-03-30 5:45 Thomas Stroesslin
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.GSO.4.21.0105030857210.28809-100000@mantrasun3.epfl.ch \
--to=thomas.stroesslin@epfl.ch \
--cc=sourcenav@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).