Thanks Mark.
>
>
> By 'brings down the whole ooRexx environment, do you mean the interpreter
> terminates, or do you mean the process crashes? I'm going to assume you
> mean the interpreter terminates.
>
Crashes is probably the best description. Windows puts up an error dialog
window saying that it's searching for a solution etc...
> As I said though, the syntax condition should be printed out. Since it
> isn't, I would say that without the terminating code, you would just see
> your program hang with no message, and have to kill rexx.exe through the
> task manager.
>
>
The Windows error dialog terminates the process when OK is pressed.
> As always, if you can produce an example that shows the problem I can most
> likely figure out what the cause is. I suspect that may be difficult in
> this case. But, if you can I'll gladly look at it.
>
>
Thanks for the offer. I managed to find the cause to the problem which was
a abc~def call where abc was .NIL, but without a message. The code
structure that is in place is similar to my last PSP example, and was
caused by a super class method not getting called early enough to set some
global attributes. As the problem is solved I don't feel that digging
deeper into this is meaningful, there are more important things in life :)
Thanks again for your explanations.
Staffan
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
