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=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC 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: David Taylor Subject: why not when others Date: 1996/09/05 Message-ID: <322F7432.7271@iquest.com>#1/1 X-Deja-AN: 178769512 distribution: world references: content-type: text/plain; charset=us-ascii organization: interQuest Online Services -- Huntsville, AL mime-version: 1.0 reply-to: dtaylor@iquest.com newsgroups: comp.lang.ada x-mailer: Mozilla 2.0 (Macintosh; I; 68K) Date: 1996-09-05T00:00:00+00:00 List-Id: Chris Sparks wrote: > > I want to thank all of the individuals who responded to my query > about the "when others" part for a case statement. My group decided > to not use "when others" so that the compiler can catch any new additions. > > Thanks Robert for the insight about "pragma Assert". Definitely a winner! > > Chris Sparks > > PS: Sorry for my ILLEGAL use of the work ERRONEOUS (pun intended) 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. dt