ed,

I would actually recommend against your approach. Not because it isn't a good one, but because Ada is a HUGE language, and (as you have found) tricky to parse. Also, there are alot of Ada tools out there already, and some that may just fit your needs. Here is what I found on Google:

Again, I would really recomend using a pre-existing tool, your likely to get much more accurate results/information. And given that you are likely working for either a Defense contractor or Aerospace firm of some kind (who the hell else uses Ada), accuracy of information, I imagine, is of paramount importance.

Again, let me re-iterate this is nothing wrong with you approach, I just don't recomend it for Ada. IMHO Ada is just to large and complex a language for this kind of approach.

NOTE:
The grammer you found is also not 100% standard Backus-Naur form either. This page describes the differences. So along with the conversion from a slightly off Backus-Naur you would need to massage it for either yacc, Parse::YAPP or Parse::RecDescent. I see alot of opportunity for loss of imformation.

-stvn

In reply to Re: Parse::RecDescent Ada95 Grammar? by stvn
in thread Parse::RecDescent Ada95 Grammar? by halley

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.