Re: Ada 0x, exception idea ?

[sk <noname@myob.com>]

strohm@airmail.net:
  > Would you please clarify?

Yes, the post you were replying to suggested parsing
the string message attached to an exception to evaluate
an error code provided in the message by Raise_Exception,
hence my response of "Yuck"

wesgroleau@myrealbox.com:
  > Why is the above (which works now) more "bulky" ...

After a brief play with it, I agree, the "case-and-raise"
syntax is a lot more elegent than a big "if-then-elsif".

However,
  > case Error_Type'Value(Ada.Exceptions.Exception_Message(E)) is
  >   when 1 =>
  >     Handle_Error_One;
quickly wanders into the realms of the unreadable.

strohm@airmail.net:
  > Observe that you get PRECISELY the same result with
  >  if Result = Bummer then raise Its_A_Bummer; end if;
  >  if Result = Darn   then raise Darn_It;      end if;
  >  if Result = Blast  then raise Blast_It;     end if;

Again, the issue isn't results, it is readability.

hyrosen@mail.com:
  > Perhaps the OP has fallen under the allure of Perl,
Haha, whenever I run across Perl, I run away and can
happily claim no base Perl motives :-)

--
This thread has diverged ...
1) concerning the simple addition to a "raise" statement.
2) the usage of Ada.Exceptions and carrying around of
error codes.

As far as the second issue goes, I have no real concerns
one way or another.

However, for the first issue, I stand by the idea that
a conditional raise statement enhances readability.

--
PS. If you stop and think about it, the whole exception
raising and handling is "syntactic sugar" anyway. To
raise an exception, code has to be in place to detect
that a requested operation cannot complete without
breaking the boundaries/parameters/context of the
requestor.

The "raise" and subsequent handlers are a shorthand,
provided by the language, to ensure that all the
necessary checks are implemented rather than relying
on the coders diligence to implement them.

-- 
-------------------------------------------------
-- Merge vertically for real address
--
--     s n p @ t . o
--      k i e k c c m
-------------------------------------------------