TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Monospaced 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
X-cc:
Sender:
"Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Subject:
From:
Philip Brashear <[log in to unmask]>
Date:
Tue, 11 Feb 1997 17:36:16 -0500
In-Reply-To:
Your message of "Tue, 11 Feb 1997 15:55:02 CST." <[log in to unmask]>
X-To:
Reply-To:
Philip Brashear <[log in to unmask]>
Parts/Attachments:
text/plain (16 lines)
James,
With respect to estimating code size expansion, the ACES does exactly that
(among other things).  If you just want these results for Ada 95, then use
the Ada 95 tests only.  Then you either run Single System Analysis or
Comparative Analysis (I can't remember which one does the size expansion
measurements -- see the documentation).  If you have to use Comp Analysis,
you can use the sample data set distributed with the ACES as your other
set of result.

Questions?

Fire away.

Phil Brashear
SIGAda PIWG Chair

ATOM RSS1 RSS2