Re: Ada Compilers

["John R. Strohm" <strohm@airmail.net>]

I'd be VERY interested in seeing a fairly detailed example on this
particular item.

Part of the GLOBAL thrust of what I'm doing is gearing myself up on Ada95,
with the idea in the back of my head of tackling some things that are
typically done in C/C++, and seeing if I can learn enough along the way to
replicate your results in a different domain area: 2x productivity, 1/4x
defect density.

Gotta do something to pass the time between job interviews and mailing out
resumes and such.

(The argument is something like this:  "Now, we all know that there really
aren't any silver bullets, right?  There really aren't any magic wands you
can wave, that will just like magic give you 2x productivity improvement and
1/4x defect density, right?  We all know that, don't we?  Well, what if
there was one?  Suppose there WAS such a wand, such a super secret magic
bullet, that really would let you tackle your current project with half as
many cars in the parking lot, that would let you write only 1/4 as many bug
reports and bug fix reports and retest reports.  If such a wand really did
exist, would you ignore it, throw it away, bury it in a landfill and post
armed guards 24/7 around it, or would you grab it and wave it for all you
were worth?")

"Marin David Condic" <dont.bother.mcondic.auntie.spam@[acm.org> wrote in
message news:acg7rd$15g$1@nh.pace.co.uk...
> If high performance is an issue for your apps, you need to *really*
> understand the language or you can generate inefficient code and be
> wondering why. You often have to experiment with alternate ways of
> accomplishing the same thing to find the one that fools the compiler into
> generating the code you want. I recall once dealing with initialization of
> some records where expressing it one way caused the compiler to go off
> making a bunch of subroutine calls, but doing it another way we got a
single
> move of a constant in memory. Know the language and experiment!