Re: Another reason for goto

[leake@cme.nbs.gov (Stephe Leake)]

In article <820@afit-ab.arpa> wbralick@afit-ab.arpa (William A. Bralick) writes:

   ...

   However, I have yet to see a case where the goto is *necessary*  It is
   a direct tweek at the program counter and is generally at too low a 
   level of abstraction for a HOL.  If time (and space) are that critical
   in a given section of code you should "goto" C (using pragma interface)
   or assembler if absolutely necessary.

Ada can be either a High level language, _or_ a low-level one. Why
should I abandon strong typing just because I need to do something
fast? If I need a fast subroutine, I write it in "low-level" ada; no
tasks, exceptions, etc; I would feel free to use a goto (although I
have yet to see a need for one). In fact, in Ada I can use single
precision, which can often cut execution in half!

Lets not limit ourselves by arbitrary notions that _all_ Ada code must
be high-level and abstract.

Stephe Leake 	(301) 975-3431 		leake@cme.nbs.gov
National Institute of Standards and Technology
(formerly National Bureau of Standards)
Rm. B-124, Bldg. 220
Gaithersburg, MD  20899