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: Richard Riehle Subject: Re: Ada naming conventions? Date: 1996/05/08 Message-ID: #1/1 X-Deja-AN: 153822200 references: <4m0fi2$225e@mule1.mindspring.com> content-type: TEXT/PLAIN; charset=US-ASCII organization: National University, San Diego mime-version: 1.0 newsgroups: comp.lang.ada Date: 1996-05-08T00:00:00+00:00 List-Id: On 28 Apr 1996, Robert Dewar wrote: > Paul said > > "I agree fully with Bob and Ken , SPC guide is a must have/must follow > guide to such things." > > Fine, just so long as "must follow" means "must follow most of the time > when appropriate". These are after all guidelines and not absolute rules. > Often turning guidelines into absolute rules makes them harmful instead > of helpful. Of course this does not apply to simple layout rules, but the > SPC guide goes far beyond that. This is one of the rare occasions where I am in full agreement with the emminent Dr. Dewar. In a 1964 issue of THINK Magazine, an IBM publication, some anonymous person on the editorial staff wrote, "The last act of a dying organization is to enlarge the rule book." Guidelines such as those in the Ada Quality and Style Guide are useful as long as they are not treated as "revealed truth," and kill the effectivness of the solution being sought. Someone in one of my Ada classes for a defense contractor once asked, "Why is it that the people who make up new rules for programmers are people who no longer write programs? Richard Riehle