#87 Enhance Condition handling doc (Ch.12 in rexxref)

None
open
5
2012-08-22
2006-08-01
D.M.Wooster
No

The coverage for traditional (non-oo) programming is
quite good, but there's little discussion anywhere
about condition handling for object oriented
programs.

Since other OO languages use the term "exception
handling" or "throwing an exception", it might be
useful to state that these are called "condition
handling" and "raising a condition", respectively, in
ooRexx. Just in case someone is searching the doc
for the other terms, they'll be brought to the right
place.

Please discuss the similarities and differences
between "signal <name of="" your="" condition="" handler="">" (I
did not mean "signal on ...") and "raise <some condition="">", since old-fashioned way to force a
condition was to signal the condition-handler.
Please include where you can and can't use each one
(e.g. signal <condition-handler> can't be used
in ::routine or ::method, if the condition-handler is
elsewhere; raise used in the mainline code
immediately kills the program, never calls
condition-handler; etc.).

Please discuss how condition handling in ooRexx
differs from exception handling in other languages.
E.G. in ooRexx nested methods/classes/routines, for
conditions that are disabled by default (user,
novalue, etc), every level must have a condition
handler and specifically propagate the condition up
to the next level, or the raised condition will be
ignored.

Please discuss any other areas where use of
directives affects the scope of visibility of
conditions.

Discussion


Anonymous

Cancel  Add attachments