From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,473e6b129c2f30cd
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!t-online.de!news.karotte.org!koehntopp.de!news.stack.nl!feeds.news.ox.ac.uk!news.ox.ac.uk!feed2.jnfs.ja.net!feed1.jnfs.ja.net!jnfs.ja.net!xara.net!gxn.net!194.159.246.34.MISMATCH!peer-uk.news.demon.net!kibo.news.demon.net!news.demon.co.uk!demon!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: ANNOUNCE: Avatox 1.0 is now available
Date: Mon, 21 Aug 2006 21:59:17 +0100
Organization: Pushface
Message-ID: <m2odudyfdm.fsf@grendel.local>
References: <JaPEg.6886$Qf.5686@newsread2.news.pas.earthlink.net>
NNTP-Posting-Host: pogner.demon.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: news.demon.co.uk 1156193957 27345 62.49.19.209 (21 Aug 2006 20:59:17
 GMT)
X-Complaints-To: abuse@demon.net
NNTP-Posting-Date: Mon, 21 Aug 2006 20:59:17 +0000 (UTC)
Cancel-Lock: sha1:XXL9ATZUFDC5712GrAJQA3D3RdA=
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (darwin)
Xref: g2news2.google.com comp.lang.ada:6305
Date: 2006-08-21T21:59:17+01:00
List-Id: <comp.lang.ada>

This is excellent news. I think I shall still carry on with my own
asis2xml (under
http://gnat-asis.sourceforge.net/pmwiki.php/Main/ASIS2XML, no releases
as yet) for a while.

I took the view that <A_DEFINING_NAME/> would look better as
<defining_name/> throughout.

There are also some interesting choices about which aspects to map
into attributes and which into child elements, and indeed on the whole
mapping to be used.

Do you support multi-unit environments?

Do you think there'd be a future in offering at least the concept to
the ASIS team?

As a demo of the sort of thing one can do, we found it pretty
straightforward to generate a report on all the exception handlers in
our application which capture non-generated exceptions, so that we
could review whether the logging being done was appropriate. The XML
for the application was >50MB, but the performance was pretty
reasonable (of order a minute to generate the report; generating the
XML took rather longer).

The guts of the XSLT report script (not at all perfect, but good
enough, and excluding some extra rules for tasks) was

  <xsl:template match="*[@unit]" mode="handlers">
    <!-- Skip 'raise ColdFrame.Exceptions.*'. -->
    <xsl:if test=".//exception_handler
                  [not(raise_statement//identifier='ColdFrame'
                  and raise_statement//identifier='Exceptions')]">
      <tr>
        <td>
          <xsl:value-of select="@unit"/>
        </td>
        <td>
          <xsl:if test=".//exception_handler[not(raise_statement)]">
            <xsl:text>Yes</xsl:text>
          </xsl:if>
        </td>
      </tr>
    </xsl:if>
  </xsl:template>

which says "for every unit that has an exception handler in it at some
level of nesting that doesn't raise one of the generated exceptions,
output a table row containg the unit name and, if the exception
handler doesn't contain a raise statement, the word 'Yes'".