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, M
Thanks to both Rony and Jean-Louis for your comments. Here are some
additional thoughts I've had as a result.
When the problem to be solved is converting one type of ordered
collection to another, as it was when I started working on this, then
the overriding principle is maintaining the order
On 17.03.2025 09:37, Till Winkler via Oorexx-devel 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 rep
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 wou
