Re: Strategies with SPARK which does not support exceptions

[Pascal Obry <pascal@obry.net>]

Yannick,

> The only one thing which seems simple and clean enough I could figure,
> is to use a Boolean variable, named “OK”, and a sequence of “if OK then”
> statements. That is, execution of one sequence of statements, which set
> OK to False is something goes wrong, and execute clean-up statements by
> the way. Then a next sequence of statements wrapped in a “if OK then”
> which do the same, and so on with next statements groups which are also
> wrapped in a “if OK then” (as many as needed).

I don't understand. SPARK code cannot raise exception, so why should the
code deal with exceptional code????

There is no exception, so not error to check... I don't see the point of
the Ok variable.

I'm probably missing something, can you clarify?

Pascal.
  Hum, while writing this I see one case where this can be used... It
  is if exceptions are used as control flow. To me this is just very
  bad practice.

-- 

--|------------------------------------------------------
--| Pascal Obry                           Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--|    http://www.obry.net  -  http://v2p.fr.eu.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver keys.gnupg.net --recv-key F949BD3B