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,99222a5bd46ef3c9 X-Google-Attributes: gid103376,public From: bobduff@world.std.com (Robert A Duff) Subject: Re: GOTO considered necessary (reworked) Date: 1997/06/17 Message-ID: #1/1 X-Deja-AN: 249466325 References: <5nn2fm$11dk$1@prime.imagin.net> <33A6A9C4.7B87@no.such.com> Organization: The World Public Access UNIX, Brookline, MA Newsgroups: comp.lang.ada Date: 1997-06-17T00:00:00+00:00 List-Id: In article <33A6A9C4.7B87@no.such.com>, Spam Hater wrote: >Even more (unfortunately) common: > "An exception is basically a goto, so don't use exceptions." An exception is even *worse* than a goto, since it's more powerful: It jumps to a run-time-determined place, which can't necessarily be determined by reading the source code. And that place can be very far away in the program (whereas a goto is local to a single subprogram). Nonetheless, it's good to use exceptions when appropriate. (It's interesting, though, that we're having a huge discussion about fine-tuning the rules-of-thumb about exactly when it is, and is not, appropriate to use goto. But I haven't seen any such discussion about exceptions.) - Bob