Thank you very much for the quick and very helpful reply! This works
very nicely! I seem to have become too fixated on using HALT. 🙂
I have an annoying followup question so. Is there an alternative to
using the "Syntax:" label which would allow me to have the check for the
4.1 syntax error in a separate file (allowing the check to be reused in
other programs)?
Best,
Till
An untrapped HALT condition gets turned into a 4.1 syntax error, which
gets automatically propagated. A single SYNTAX condition trap at the
top level can check the error number. If it's 4.1, process as a halt
condition, otherwise propagate the syntax error so it's handled normally.
Rick
On Mon, Mar 17, 2025 at 4:38 AM Till Winkler via Oorexx-devel
<oorexx-devel@lists.sourceforge.net> wrote:
I'm trying to catch user interrupts (typically triggered by: CTRL
+ C).
While I managed to gain a working example (see attached), I was
wondering if there might be a better way to deal with it?
In particular, I would like to avoid the repetition of labels (in the
example: “propagate:”) and it would be nice to collect all labels (in
the example: “propagate:” and “halt:”) in a single place and even in a
separate file.
Hope someone has an idea for this!?
Best,
Till
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
