TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Proportional Font
Show HTML Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
"Team Ada: Ada Programming Language Advocacy (83 & 95)" <[log in to unmask]>
Subject:
From:
Karl Nyberg <[log in to unmask]>
Date:
Wed, 15 Dec 2004 07:24:56 -0500
In-Reply-To:
<[log in to unmask]> (message from Chris Sparks on Wed, 15 Dec 2004 03:59:29 -0800)
X-To:
Reply-To:
Parts/Attachments:
text/plain (17 lines)
ASIS is the Ada Semantic Interface Specification.  It's basically an
abstract interface into the underlying compiler's data structures.  With it,
you can build code that queries the data structures created by the compiler
and then write tools that use those structures.  There's an ASIS4GNAT
project hosted as http://www.sourceforge.net and there's also an ASIS
library with the OCS PowerAda compiler that I've used.  I suspect other
compilers also provide such an interface.

See http://www.acm.org/sigada/WG/asiswg/ for an introduction.

But using an ASIS implementation generally requires starting with compiled
Ada code. I think you're going the other way, right?  What I meant to
suggest was that you look into whether you wanted to map your C++ classes as
a private type, tagged type or variant record based on the methods in use.

-- Karl --

ATOM RSS1 RSS2