Re: Localized Variable Declaration

["Marin David Condic" <dont.bother.mcondic.auntie.spam@[acm.org>]

C and C++ programmers tend to write things without spaces or underscores, so
you can tell their origin when you see Ada code that looks like:

SomeProcedureName(X,Y,Z);

Ada programmers make more frequent use of spaces and underscores, so it is
much more common to see:

Some_Procedure_Name (X, Y, Z);

To a large extent, it is a matter of taste, but you can use the ARM and Ada
Quality & Style as good guidelines. In general, I suggest this: When working
on a program someone else wrote, stick to whatever style they used. When
working on a group project, get everyone to agree to some style and stick to
it - but avoid nit-picking arguments over every single comma or space. When
working strictly on your own, use any style you like - but be consistent.

There are various tools that can be used to format Ada code and their use
will bring you a certain consistency, but I've never found them to be a 100%
substitute for hand-formatting and I've not encountered one that ever
formatted things the way *I* would do it. :-) (Well, except for one I wrote
a bunch of years ago for Ada83 - and even then, my style has evolved since
then & it doesn't work for Ada95. :-)

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com


"Michael Bode" <m.g.bode@web.de> wrote in message
news:m37klhkk02.fsf@jupiter.solar.system...
>
> Could someone please help a poor Ada beginner and tell me when to
> leave a blank between a function name and its parameter list and when
> not? I personally find the above Put_Line("write two number"); more
> readable than Float := Float (a) * Float (b) * 42.42; because I think
> of a function and its parameters as a unity, but I've seen the blanks
> in textbooks quite often. OTHO "Ada Quality and Style" favors the
> Put_Line(...)
>
> PS: No Holy War intended.