comp.lang.ada
 help / color / mirror / Atom feed
From: Ken Garlington <garlingtonke@lmtas.lmco.com>
Subject: Re: Coding Standards
Date: 1996/05/28
Date: 1996-05-28T00:00:00+00:00	[thread overview]
Message-ID: <31AABC53.1080@lmtas.lmco.com> (raw)
In-Reply-To: DrGtEE.EtF@world.std.com


Robert A Duff wrote:
> 
> By the same argument, why should programmers have to read the Ada
> manual?  After all, if you can't understand or maintain the code without
> the Standard, then the language standard is not making the code more
> readable.  For example, if you don't understand the type checking rules,
> then type checking won't help you understand the program.  ;-)

(Oops - let's try that again...)

Funny you should mention this. We have a lot of non-programmers that read
(but do not modify) our Ada code. These folks include hardware engineers,
test engineers, etc. who need to understand a particular detail about
an algorithm. They rarely have to resort to an Ada manual to
understand a type definition. This is the wonderful thing about Ada: It's
fairly intuitive to read. Or at least, it should be. I gather you feel
differently. Certainly, I would expect someone _modifying_ the code to be 
familiar with how the language works, which they could get from the ARM.
However, I've often reused code successfully without any knowledge of the
original coding standards.

It also seems to me that your argument regarding the language manual is also
deficient, in that it assumes that if requring knowledge from one source is
necessary, that requiring knowledge from two sources is better. If that's the
case, why not use obscure sequences of letters for all declarations, with a 
third document definining what these sequences actually mean?  Generally, I
would think the _less_ complicated you make the process of understanding and
maintaining software, the better.

> I can assure you that if you work on a project where I'm the boss, and
> it's written in Ada, you will be required to know Ada, and to know
> project-wide conventions about Ada, and so on.

This still begs the question I've asked on a couple of occasions: What
happens when your code is used on my project? If I reuse your code, am
I forced to use your coding standards, in order to keep the code maintainable?
This would seem to be a significant deterrent to its reuse.

-- 
LMTAS - "Our Brand Means Quality"




  reply	other threads:[~1996-05-28  0:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-05-15  0:00 Coding Standards W. Wesley Groleau (Wes)
1996-05-15  0:00 ` Robert A Duff
1996-05-28  0:00   ` Ken Garlington [this message]
1996-05-28  0:00     ` Robert A Duff
1996-05-29  0:00       ` Ken Garlington
1996-05-30  0:00       ` Frank Manning
1996-05-28  0:00   ` Ken Garlington
1996-05-16  0:00 ` Ken Garlington
1996-05-17  0:00   ` Richard A. O'Keefe
1996-05-17  0:00     ` Ken Garlington
1996-05-20  0:00       ` Richard A. O'Keefe
1996-05-20  0:00         ` Ken Garlington
  -- strict thread matches above, loose matches on Subject: below --
1996-05-17  0:00 W. Wesley Groleau (Wes)
1996-05-28  0:00 ` Ken Garlington
1996-05-29  0:00 W. Wesley Groleau (Wes)
1996-05-29  0:00 ` Ken Garlington
1996-05-29  0:00 ` Robert A Duff
1997-09-17  0:00 Is there an ADA analogue to the C++ continue statement? Heath, Terry D.
1997-09-18  0:00 ` Pascal Obry
1997-09-19  0:00   ` Robert Dewar
     [not found]     ` <3422F037.41CA@lmco.com>
1997-09-20  0:00       ` dan13
1997-09-21  0:00         ` Robert Dewar
     [not found]           ` <3426B51E.7296@lmco.com>
1997-09-23  0:00             ` Coding Standards W. Wesley Groleau x4923
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox