Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#713 Untrapped "halt" condition not turned into a syntax conditio

v4.0
closed
Rick McGuire
5
2012-08-14
2009-05-31
No

According to the docs (rexxref.pdf, chapter 11.1, "Action Taken when a Condition is Not Trapped") an untrapped halt condition will cause the interpreter to create an appropriate syntax condition.

However, if having a Rexx program issue the keyword statement "raise halt", does not cause a syntax error to be generated, if that condition is not trapped.

If usiing the archive of
https://sourceforge.net/tracker/?func=detail&aid=2799237&group_id=119701&atid=684730, then the following could be entered on a command line to study the effects.

a) rexx.exe: just cause a untrapped halt condition to be raised by "02_second.rex"; will not raise a syntax condition
rexx 01_first.rex name=a raise=halt

b) simpleRW.exe: will invoke "01_first.rex" with the same arguments as a) above; upon return ConditionCheck() returns 0 (unexpected!)
simpleRW.exe name=b_native raise=halt

c) rexx.exe: cause a syntax condition to be raised by "02_second.rex", trap it in "01_first.rex";will trap the halt condition, o.k.
rexx 01_first.rex name=c raise=halt signalon

d) simpleRW.exe: will invoke "01_first.rex" with the same arguments as c) above; upon return ConditionCheck() returns 0 (o.k.)
simpleRW.exe name=d_native raise=halt signalon

Discussion


Anonymous


Cancel   Add attachments