From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,15890893c0618a8a
X-Google-Attributes: gid103376,public
From: falk@hendrix.dsd.northrop.com (Frank Falk)
Subject: Re: [Q] Tools for Ada Quality and Style
Date: 1996/04/30
Message-ID: <4m5t0p$gig@esdmaster.dsd.northrop.com>#1/1
X-Deja-AN: 152287870
distribution: world
references: <9604172134.AA27114@eight-ball> <767968529wnr@diphi.demon.co.uk>
 <4xenp57jj1.fsf@leibniz.enst-bretagne.fr>
organization: Northrop Corporation ESD-RMS
newsgroups: comp.lang.ada
Date: 1996-04-30T00:00:00+00:00
List-Id: <comp.lang.ada>


I used Rational APEX on my last project.  It not only pretty printed
code for me, but corrected my errors.

I use to love the way it would decide that if I nested if-then statements
and forgot an "end if" it was the last one I forgot.  Of course after redoing my
indentations, my code no longer do what I wrote, but it looked nice. :)  Finding 
where to place those two words after my indentations were "fixed" led to many
happy and productive hours.

The joy of putting something where it didn't belong and having APEX "fix" it also
gave me many hours of joy. :)

I believe there was a switch to turn this feature off, along with a switch to
align colons, but it was decided at the project level not to set them.

In closing, let me say that if I had the choice to use it again, I would.  It 
might be very expensive but on a large project it will pay for itself.