TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Steffen Bretz <[log in to unmask]>
Reply To:
Steffen Bretz <[log in to unmask]>
Date:
Mon, 15 Sep 2003 18:23:05 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
Hi,

I agree with you with the positive effects verbose coding.
Excessive use of the use clause makes a program hard to read,
especially if packages are "use"d which are not standard. But
I feel free to use it for packages wich are defined by the
language - everybody knows them anyway. Sometimes I use the
use clause also for self written packages, but only if it
seemes to me to be clearly arranged (few lines of code and
only one use).

I seldomly name the parameters. The compiler can (and does)
pay attention, that the parameter positions are not changed
 - thanks to the type system. In cases where multiple parameters
have compatible types, I find the parameter naming very usefull
to garantuee a correct handing-over.

An important thing for me is the use of verbose variable names.
I never use abbreviations. If the lines of code become to long,
verbose variable names can easily abbreviated in an local area
with the renaming statement. A declare block with the renaming
statements reads then like a legend.

One character names like i, j or k are used by me only to code
mathematical formulars so that they have similar variable namings
like in math books. They are usually indices and thus loop
variables.

So long,
Steffen Bretz

ATOM RSS1 RSS2