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=-2.9 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,577df5d4a0e88785 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2000-12-15 22:10:24 PST Path: supernews.google.com!sn-xit-02!supernews.com!isdnet!enst!enst.fr!not-for-mail From: "Robert C. Leif, Ph.D." Newsgroups: comp.lang.ada Subject: RE: Bad coding standards Date: Fri, 15 Dec 2000 22:08:11 -0800 Organization: ENST, France Sender: comp.lang.ada-admin@ada.eu.org Message-ID: Reply-To: comp.lang.ada@ada.eu.org NNTP-Posting-Host: marvin.enst.fr Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: avanie.enst.fr 976947013 16763 137.194.161.2 (16 Dec 2000 06:10:13 GMT) X-Complaints-To: usenet@enst.fr NNTP-Posting-Date: Sat, 16 Dec 2000 06:10:13 +0000 (UTC) To: Return-Path: X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <91dh7c$44t$1@nnrp1.deja.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Errors-To: comp.lang.ada-admin@ada.eu.org X-BeenThere: comp.lang.ada@ada.eu.org X-Mailman-Version: 2.0beta5 Precedence: bulk List-Id: comp.lang.ada mail<->news gateway Errors-To: comp.lang.ada-admin@ada.eu.org X-BeenThere: comp.lang.ada@ada.eu.org Xref: supernews.google.com comp.lang.ada:3198 Date: 2000-12-15T22:08:11-08:00 From: Bob Leif To: Ted Dennison et al. Although, "often the old names *and* the new names will be used in the body of that package", is a possibility, locating the renames in one prominent place will significantly reduce the probability of it occurring. I might also note, that one should with packages that are specific to a body at the level of the body not the specification. The renames in the body should also be contained in a table of contents. -----Original Message----- From: comp.lang.ada-admin@ada.eu.org [mailto:comp.lang.ada-admin@ada.eu.org]On Behalf Of Ted Dennison Sent: Friday, December 15, 2000 8:35 AM To: comp.lang.ada@ada.eu.org Subject: RE: Bad coding standards In article , comp.lang.ada@ada.eu.org wrote: > A very simple solution to producing and using a name with a reasonable > length is to do all the renames at the beginning of the Ada source. > This produces a Table of Contents. In fact, if one uses any but the > most common abbreviations for any purpose, the also should be listed > together. One of the beauties of Ada is the source text can be > organized as a readable technical document. The problem with that approach is that often the old names *and* the new names will be used in the body of that package. That's just gawd-awful. This is particularly likely to happen if multiple people end up helping to author the source file. Each tends to have their own favorite way of naming things. As we are rather fond of pointing out to C coders, just because some feature *can* be used to make readable code doesn't mean it typically *will* be used that way. -- T.E.D. http://www.telepath.com/~dennison/Ted/TED.html Sent via Deja.com http://www.deja.com/