Re: Evaluating Ada compilers -- any experiences, tips?

[n_brunot@my-deja.com]

We don't have experience in cross-platform compilers, but with same
target/host platform, we find very good to always have several
compilers checking every day (just run compilation after day work, and
check in the morning than it's ok), and only one for tests and release
versions.
This allows you to keep ADA code as independant as possible from the
compiler (in case that one day you have to change it for any reason),
and may be detect one day than one of your checking compiler is better
than your release compiler.
More than that, a bad compiler can be easier and faster to use for
writing code and syntax check, supposing of course than tests and
release versions are compiled with the good compiler, but may be not so
fast and easy to use.

see subject Windows NT ADA compilers comparison on this forum.

In article <8m9l8c$3g2$1@nnrp1.deja.com>,
  mjsilva@my-deja.com wrote:
> While we're waiting to see if we've made a convincing argument for
> using Ada in our industrial controller proposal I'm back to looking at
> compilers.  I've sent off info requests to all of the compiler vendors
> I could find, but I'd like to hear any experiences or info (positive
or
> negative) with Ada toolsets regarding e.g. compiler quality, support,
> long-term commitment to Ada, etc.
>
> Our target is the PowerPC MPC555, and the host will be Windows.
>
> Here's my email address if anybody wants to respond privately:
>
> msilva@amotusa.com
>
> Thanks much for any help!
>
> Mike
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>


Sent via Deja.com http://www.deja.com/
Before you buy.