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,86fd56abf3579c34 X-Google-Attributes: gid103376,public From: dewar@cs.nyu.edu (Robert Dewar) Subject: Re: State machines and Goto's (was Re: Should internet support software be written in Ada?) Date: 1995/04/07 Message-ID: #1/1 X-Deja-AN: 100070412 references: <3kaksj$iur@isnews.calpoly.edu> <3ki9t8$c8l@Starbase.NeoSoft.COM> <3ldnmh$hi5@maple.enet.net> <3line1$ma0@nic.umass.edu> <3lt00o$rgf@gnat.cs.nyu.edu> <3m0nv5$67l@theopolis.orl.mmc.com> organization: Courant Institute of Mathematical Sciences newsgroups: comp.lang.ada Date: 1995-04-07T00:00:00+00:00 List-Id: T.E.D. asks a difficult question. He wants an absolute set of coding rules. But with regard to GOTO's no absolute set of rules is likely to be a good choice. Probably any formalized set of coding standards should say GOTO's are not allowed. I am worried that if you try to codify the conditions under which GOTO's are reasonable, you will create a backdoor for incompetent programmers to commit crimes against Ada. Of course incompetent programmers will commit such crimes in any case, regardless of standards. Still ... The real point is that any usable set of coding standards must have some flexibility. You get a similar problem trying to describe when the use of unchecked conversion is OK.