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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE,
	MSGID_SHORT autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!attcan!uunet!crdgw1!jupiter!kassover
From: kassover@jupiter.crd.ge.com (David Kassover)
Newsgroups: comp.lang.ada
Subject: Re: On quitting an iterator prematurely
Message-ID: <6827@crdgw1.crd.ge.com>
Date: 13 Apr 90 22:04:22 GMT
References: <9004041704.AA17624@ajpo.sei.cmu.edu> <1151@enea.se> <120.26224a7e@wsuiar.uucp>
Sender: news@crdgw1.crd.ge.com
Organization: Aule-Tek, Inc.
List-Id: <comp.lang.ada>

In article <120.26224a7e@wsuiar.uucp> tdhammer@wsuiar.uucp writes:
...
>
>Perhaps this is an argument for an extension to the optional parameters
>to include out parameters that may or may not appear in the procedure
>call?  That would be an interesting implementation.

Would that not require that the compiler *not* verify that the
out parameter is the target of an assignment?  An important
check, no?

Perhaps an optional in out parameter, where the parameter is
guaranteed to have at least the default value would work
acceptably.


I, myself, see nothing wrong with specifying a routine that
raises an exception (and specifying the name of that exception).
Therefore one can write an exception handler to interpret the
exception as is appropriate in the outer routine.

For example:  Several routines that I use can raise the
exception FILE_NOT_FOUND.

This does not mean to me that this is an error.  In fact, the
presence of the file, and the not-raising of FILE_NOT_FOUND may
indicate that an error has occurred.

This question of "misuse" of Ada exceptions begins to remind me
of the jihad between the structured programming mullahs who
maintain that loops must be exited only in one place, and the
rest of us in the real world, who know better.


"A foolish consistency is the hobgoblin of small minds"
			-with apologies to Emerson

--
===================================================
David Kassover
kassover@ra.crd.ge.com
kassover@crd.ge.com