Re: [Oorexx-devel] Error message when breaking a running ooRexx program

2019-11-06 Thread Rick McGuire
It is NOT the entire program. For example, the SAY instruction invokes methods on a stream object. If the halt is detected during the processing of one of those methods, then their is not halt condition handler in effect and this gets converted into an error condition. Rick On Wed, Nov 6, 2019

Re: [Oorexx-devel] Error message when breaking a running ooRexx program

2019-11-06 Thread P.O. Jonsson
> Am 06.11.2019 um 22:04 schrieb Rick McGuire : > > It all depends on whether the bit of code where the halt condition is > detected has SIGNAL ON HALT enabled or not. The Monitor class UNKNOWN method > is not one of those locations, so the HALT condition gets turned into an > error because

Re: [Oorexx-devel] Error message when breaking a running ooRexx program

2019-11-06 Thread P.O. Jonsson
Ok, thanks, this makes sense. Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 06.11.2019 um 22:02 schrieb Rick McGuire : > > That is just the traceback showing you the call chain from where the halt was > originally detected. Execution was in the UNKNOWN method of the Monitor

Re: [Oorexx-devel] Error message when breaking a running ooRexx program

2019-11-06 Thread Rick McGuire
It all depends on whether the bit of code where the halt condition is detected has SIGNAL ON HALT enabled or not. The Monitor class UNKNOWN method is not one of those locations, so the HALT condition gets turned into an error because it was not handled. Rick On Wed, Nov 6, 2019 at 3:11 PM P.O.

Re: [Oorexx-devel] Error message when breaking a running ooRexx program

2019-11-06 Thread Rick McGuire
That is just the traceback showing you the call chain from where the halt was originally detected. Execution was in the UNKNOWN method of the Monitor class, which is one of the builtin ooRexx classes. Since these classes reside in the interpreter image, which does not include the original source,

Re: [Oorexx-devel] Error message when breaking a running ooRexx program

2019-11-06 Thread P.O. Jonsson
Adding signal on halt only helps every now and then, most of the time I get the same error message, maybe the loop is too tight? Hello /bin/sh: YOU: command not found 6 *-* You pressed halt >>> "YOU PRESSED HALT" +++ "RC(127)" Most of the time I still get this: ^CHello

Re: [Oorexx-devel] Error message when breaking a running ooRexx program

2019-11-06 Thread P.O. Jonsson
I did not mean the actual (expected) outcome of pressing break, I meant this error message: > Method UNKNOWN with scope "Monitor" in package "REXX" (no source available) What source is not available? How shall I understand the scope „Monitor“ of an unknown method? Where can I read up on this

Re: [Oorexx-devel] Error message when breaking a running ooRexx program

2019-11-06 Thread Walter Pachl
SureTry Signal On HaltDO WHILE 1>0 say 'Hello' ENDhalt: Say 'you decided to end the loop' Say 'Good bye'  "P.O. Jonsson" hat am 6. November 2019 um 19:42 geschrieben: Hi,I got this error message when pressing C  on a program running and getting stuck in a loop. I have enclosed a simpler

[Oorexx-devel] Error message when breaking a running ooRexx program

2019-11-06 Thread P.O. Jonsson
Hi,I got this error message when pressing C  on a program running and getting stuck in a loop. I have enclosed a simpler example.   361 *-* Method SAY with scope "Stream" in package "REXX" (no source available).  1448 *-* Method UNKNOWN with scope "Monitor" in package "REXX" (no source