TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
From: Philip Brashear <[log in to unmask]>
Date: Tue, 11 Feb 1997 19:16:55 -0500
In-Reply-To: Your message of "Tue, 11 Feb 1997 17:48:42 CST." <[log in to unmask]>
Reply-To: Philip Brashear <[log in to unmask]>
Parts/Attachments: text/plain (8 lines)
Phil (Johnson) reminds me that the ACES code size measurement applies only
to the actual code segment under test, and that the total executable size
may be more in line with what you want.  As is always the case with
performance assessment, it depends on what you're looking for.  When your
only tool is a hammer (in my case, the ACES), everything looks like a nail.

Phil (Brashear)