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,fac1372a6e25492a
X-Google-Attributes: gid103376,public
From: Robert A Duff <bobduff@world.std.com>
Subject: Re: Ada Protected Object Turorial #2: Overview of Tasks
Date: 1999/12/23
Message-ID: <wccpuvxadvz.fsf@world.std.com>#1/1
X-Deja-AN: 564212641
Sender: bobduff@world.std.com (Robert A Duff)
References: <83hu2h$bba$1@bgtnsc01.worldnet.att.net>
 <83j1g0$ck4$1@nnrp1.deja.com> <wcc7li7uhii.fsf@world.std.com>
 <83sb6f$r3g$1@nnrp1.deja.com>
Organization: The World Public Access UNIX, Brookline, MA
Newsgroups: comp.lang.ada
Date: 1999-12-23T00:00:00+00:00
List-Id: <comp.lang.ada>

Robert Dewar <robert_dewar@my-deja.com> writes:

> It would be like saying that since exceptions are a form of
> non-local gotos, that it makes sense to allow general non-local
> gotos :-)

Interesting.  You're obviously implying that the above argument is
patently absurd, but I'm not so sure it is!  ;-)

I used to use non-local gotos in Pascal once in a while, and I didn't
find them so horrible.  At least with a goto, you know where you're
going to.  Exceptions are less readable, in the sense that you might be
jumping to who-knows-where.  (Of course that's the whole *point* of
exceptions -- to separate the detection of an exceptional situation from
the determination of what to do about it.)

Of course non-local gotos in Ada would make no sense: I can't imagine
what it would mean to goto from a procedure into a different task, and
Ada doesn't provide any way to tell (at compile time) what tasks are
running what procedures.

- Bob