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: mfb@mbunix.mitre.org (Michael F Brenner)
Subject: Re: GOTO considered necessary (reworked)
Date: 1997/06/12
Message-ID: <5nonfk$rcr@top.mitre.org>#1/1
X-Deja-AN: 248856963
References: <5nn2fm$11dk$1@prime.imagin.net>
Organization: The MITRE Corporation, Bedford Mass.
Newsgroups: comp.lang.ada
Date: 1997-06-12T00:00:00+00:00
List-Id: <comp.lang.ada>


Comment: section 3 (b) on efficiency should be moved up to being
the primary reason for using GOTOs in FSAs, other posts notwithstanding.
Reasons include lack of perfect inlining, lack of perfect code hoisting,
lack of perfect hardware caching, and other specific examples which
I have to post since some people apparently really believe
that it is a stylistic issue and not an efficiency issue. A clear
efficiency difference can be shown with both a regular-expression
oriented finite state transducer, such as an automatic group or a
awk-like find-and-replace pattern, and with a Domulke bit-matrix
style parser.