Re: Code flow control

["Randy Brukardt" <randy@rrsoftware.com>]

"Kevin Chadwick" <kevc3no4@gmail.com> wrote in message 
news:23031592-5a56-4d56-bda7-34877588802dn@googlegroups.com...
On Friday, 15 October 2021 at 21:02:49 UTC+1, G.B. wrote:
> On 15.10.21 20:03, Dmitry A. Kazakov wrote:
> > On 2021-10-15 19:48, J-P. Rosen wrote:

>> >> Some people reserve exceptions for signalling errors. I regard them as 
>> >> a way to handle "exceptional" situations, i.e. when the normal flow of 
>> >> control cannot continue. For example, in a deep recursive search, they 
>> >> are handy to stop the recursion and go back to top level when you have 
>> >> found what you were looking for. Some would disagree with that.
>> >
>> > I strongly believe that this is the only consistent way to treat 
>> > exceptions.
>> Once found, pass the result to the party that needs it.
>> Then, finish the computational task that found the result.
>> Is there anything besides exceptions to do that, and orderly?

>I believe the ada 95 style guide recommended a standard goto?

Gotos only work within a single invocation of a single subprogram. It is 
rarely the case that some complex computation only uses one subprogram, and 
that's never the case in a recursive search (the example that J-P gave).

A program that tries to handle end-of-file by calling End_of_File all over 
is (a) way more complex than necessary, and (b) likely to be wrong as some 
case is missed. Handling End_Error makes way more sense.

Of course, if you *are* in a single subprogram, then the advice of the style 
guide is good (exceptions having more overhead than gotos, especially when 
they actually occur). They're best used when multiple subprograms (or 
subprogram calls) are involved.

                              Randy.