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.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 2002:a24:6283:: with SMTP id d125mr2856526itc.14.1553034984207;
        Tue, 19 Mar 2019 15:36:24 -0700 (PDT)
X-Received: by 2002:a9d:64c1:: with SMTP id n1mr3343159otl.187.1553034983940;
 Tue, 19 Mar 2019 15:36:23 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!i2pn.org!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!w126no17626ita.0!news-out.google.com!l81ni54itl.0!nntp.google.com!78no18023itl.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Tue, 19 Mar 2019 15:36:23 -0700 (PDT)
In-Reply-To: <q6rphu$arn$1@franka.jacob-sparre.dk>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=96.255.209.31;
 posting-account=zwxLlwoAAAChLBU7oraRzNDnqQYkYbpo
NNTP-Posting-Host: 96.255.209.31
References: <b196da6e-4614-42f9-9147-b1708c6e5094@googlegroups.com>
 <c16f6c7d-34d9-4d7e-96e6-9c00e387b2a9@googlegroups.com>
 <q66m95$8ri$1@dont-email.me>
 <a534f338-a418-424e-8043-31c738682807@googlegroups.com>
 <q68mv0$rea$1@dont-email.me>
 <a4ab4f3c-9151-47c7-9d3f-f6a23451fa0e@googlegroups.com>
 <bba8f6a8-36ce-4bed-bd84-8a9ea7dc02f7@googlegroups.com>
 <q699nu$ban$1@franka.jacob-sparre.dk>
 <6e1977a5-701e-4b4f-a937-a1b89d9127f0@googlegroups.com>
 <q6pa1g$3j7$1@franka.jacob-sparre.dk>
 <6f9ea847-2903-48c8-9afc-930201f2765a@googlegroups.com>
 <q6qa4u$kd0$1@gioia.aioe.org>
 <f4eee526-e607-4e1f-843f-9913c9c093f9@googlegroups.com>
 <q6rphu$arn$1@franka.jacob-sparre.dk>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <de2f5462-fa10-4fdf-97a6-99989e40c697@googlegroups.com>
Subject: Re: Intervention needed?
From: Optikos <optikos@verizon.net>
Injection-Date: Tue, 19 Mar 2019 22:36:24 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: reader01.eternal-september.org comp.lang.ada:55903
Date: 2019-03-19T15:36:23-07:00
List-Id: <comp.lang.ada>

On Tuesday, March 19, 2019 at 6:13:20 PM UTC-4, Randy Brukardt wrote:
> "Optikos" wrote in message=20
> news:f4eee526-e607-4e1f-843f-9913c9c093f9@googlegroups.com...
> ...
> >Absolutely not.  The cursor cannot dangle after the finalization of the=
=20
> >container.
> >No dangling after container-finalization means no dangling-of-cursor at=
=20
> >all. Q.E.D.
>=20
> Baloney. The cursor object still exists, and someone can still try to use=
=20
> it. Yes, you'll get an =E2=80=A2=E2=80=A2=E2=80=A2exception=E2=80=A2=E2=
=80=A2=E2=80=A2 rather than erroneous execution

No, you have it all wrong =E2=80=A2=E2=80=A2=E2=80=A2there=E2=80=A2=E2=80=
=A2=E2=80=A2.  Not raise an exception, but rather gracefully take the end-o=
f-walk branch of code, just as in normal operations.  Nothing exceptional a=
bout it.  Cursors have as their fundamental mission to walk a (portion of a=
) container until the end-of-walk conditional branch is taken instead, mean=
ing that the walk reached its natural terminus.  No raise.  No exception.  =
Nothing aberrant.  Just end of the walk.  Just
1) the else branch taken instead of the then branch
or
2) exit loop taken instead of another iteration.