From: "Ingold Chuck (NMP/Boston)" <Chuck.Ingold@nokia.com>
To: <sourcenav@sources.redhat.com>
Subject: macro database in 5.0
Date: Tue, 31 Jul 2001 08:46:00 -0000 [thread overview]
Message-ID: <B9CFA6CE8FFDD211A1FB0008C7894E460477A575@bseis01nok> (raw)
Hi,
Congrats and thanks for an excellent tool!
I've had a great time examining source code by reading your database
files from Python.
My question concerns the macro database.
I've dumped the contents with dumpdb.exe, and
the start_position and end_position seem to refer to the macro symbol
rather then the content of the macro. Is this intended?
Example:
// Line 27 of Myfile.c follows
#define MY_STRING "Some text"
The entry dumped from the .ma file looks like
MY_STRING 000027.0008 C:/test/Myfile.c;000027.0017 0x0 {} {} {} {}
while I would expect a line like
MY_STRING 000027.0008 C:/test/Myfile.c;000027.0029 0x0 {} {} {} {}
which covers the content of the macro.
That would match the behavior of the .fu entries.
Or maybe I'm not seeing something clearly
-- Chuck
reply other threads:[~2001-07-31 8:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=B9CFA6CE8FFDD211A1FB0008C7894E460477A575@bseis01nok \
--to=chuck.ingold@nokia.com \
--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).