Re: aunit?

[Georg Bauhaus <sb463ba@d2-hrz.uni-duisburg.de>]

Stephen Leake <Stephen.A.Leake@nasa.gov> wrote:
: 
: If code is not "properly formatted", I sometimes
: spend enough time being bothered by it that it's worth fixing.

In my view "worth fixing" needs careful consideration.
The bulk of -gnaty warnings is about issues which can or
cannot be an improvement, depending on settings entirely
outside the control of GNAT. Whether or not a space before
a paren is a good thing depends, among other things, on
the fonts used, and on the medium used to display the Ada
source code. (consider f (x) in most various circumstances.)
Seen this way one might argue that -gnaty is
completely unaware of any typographical tradition in mathematical
typesetting. It seems to be aware of typical font appearance
in typical plain text editors, on typical low res displays, as preset.
That is, fixed width Courier, typically _not_ by IBM, but by
Monotype or Adobe. Or, on character terminals, aware of the screen
font that comes with your VGA, for example.

Consistent indentation is a different, unrelated matter.

I wish one could ask -gnatyX to concentrate on those aspects
of source code which render Ada text ambigous to the human eye,
like using l near 1 (or using l at all. Isn't there a "k instead
of i in GNAT" policy?).

Source code might look familiar because of the same spacing
applied between tokens. But does this make you familiar with
the source code? To each his own, yes. Ophelia doesn't sound
like Hamlet, and that play will change a bit if you make them
sound alike. I don't see the same danger for Ada source code,
but I do see the time spent. My preference is (mostly) to 
learn how to read code that I haven't written, and only suggest
-gnaty like improvements in case of a deeply nested mess.

-- Georg