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,3b21d694de03460e X-Google-Attributes: gid103376,public From: dewar@cs.nyu.edu (Robert Dewar) Subject: Re: why not when others Date: 1996/09/06 Message-ID: #1/1 X-Deja-AN: 178889602 references: <322F7432.7271@iquest.com> organization: Courant Institute of Mathematical Sciences newsgroups: comp.lang.ada Date: 1996-09-06T00:00:00+00:00 List-Id: David said "If you are working on a large program of approx 1M semicolons and have 40 programmmers and many interdependent parts and an overly ambitious schedule and your best change assessment tool is grep, you will learn to program defensively by doing such things as not using "when others" whenever possible. Learn to make the compiler do as much of the grunt work as you can." not to mention choosing the language that will do as much of the grunt work as possible. perhaps that can be a slogan for Ada 95: The language that takes the grunt work out of programming :-)