From: "Richard F Weber" <rfweber@link.com>
To: sourcenav@sourceware.cygnus.com
Subject: Parsing Question
Date: Wed, 04 Apr 2001 06:52:00 -0000 [thread overview]
Message-ID: <3ACB2710.9000700@link.com> (raw)
To all of the parser writers out there, If this isn't the right place
to submit questions like this, then let me know how else to submit them.
But in any case, question with regards to Creating symbols & the such.
For those of you not familiar, I'm working on an Ada parser right now.
I've got some success in doing basic preliminary type stuff, but I've
got an interesting question on how to approach something.
In Ada, you have .ads files (like header files) and .adb files (which is
the body of code). As such, a file called abc.adb, almost requires that
you have a class called "abc" defined in abc.adb. However, in the
abc.ads file, you have the declaration of the class abc, as well as
member functions and variables.
My hang up is when I come across the symbol identifying a class
definition in the .adb file, I do a sn_insert_symbol(SN_CLASS_DEF), but
in the .ads file, there is no way to do an
sn_insert_symbol(SN_CLASS_DCL). So should I be doing a class
declaration, or something else to indicate where the class itself is
declared. The only other CLASS related definition is SN_CLASS_INHERIT,
but I'm not really inheriting anything. Am I on the right track, or am
I doing something just flat out wrong.
One other quick question, how do I submit the diff's to get color coding
of Ada working. Even if the parser isn't done yet, I'd like to see the
color coder in as well. (Maybe even get around to doing one for Perl as
well)
Thanks
--Rich
reply other threads:[~2001-04-04 6:52 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=3ACB2710.9000700@link.com \
--to=rfweber@link.com \
--cc=sourcenav@sourceware.cygnus.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).