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.8 required=5.0 tests=BAYES_00,INVALID_DATE, MSGID_SHORT autolearn=no autolearn_force=no version=3.4.4 Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!crdgw1!ge-dab!puma!andrew.ATL.GE.COM!jnixon From: jnixon@andrew.ATL.GE.COM (John F Nixon) Newsgroups: comp.lang.ada Subject: Re: if UNIX then USE_C ?? (was: Reasons for drop) Message-ID: <209@puma.ge.com> Date: 26 Feb 90 20:55:58 GMT References: <27187@cup.portal.com> <18175@megaron.cs.arizona.edu> <5476@crdgw1.crd.ge.com> <34196@news.Think.COM> <5518@crdgw1.crd.ge.com> <204@puma.ge.com> <5563@crdgw1.crd.ge.com> Sender: news@puma.ge.com List-Id: kassover@jupiter.crd.ge.com (David Kassover) writes: >No need to apologize, I *was* thinking of FORTRAN, specifically >that example, since we discussed it in particular. Whoops, I though you were talking about C. >But it is possible to make single character mistakes in C. It is possible to make single character mistakes in Ada. Suppose I have a loop named MISSLE_A and a loop (interior to MISSLE_A) named MISSLE_B. I can "exit" a named loop, and screw up the name. Admittedly a contrived example, but the principle extends to anything with a name (identifiers, types, ...). Nothing in *Ada* prevents this, only the discipline of the software developer. C does have several built in traps (= vs. ==), but there are ways of dealing with these problems at the developer level. ---- jnixon@atl.ge.com ...steinmetz!atl.decnet!jnxion