To execute a program with an interpreter instance, one can get a thread
context and then use -CallProgram(name, array), which expects the
program to be stored in a file named name, supplying it with the
arguments in array.
However, if Rexx scripts are passed via a buffer (e.g. retrieved from
There is no CallProgramFromData(), but you can use NewRoutine() to
create a routine object and call thatwhich is essentially the
equivalent.
Rick
On Mon, May 11, 2009 at 12:10 PM, Rony G. Flatscher
rony.flatsc...@wu-wien.ac.at wrote:
To execute a program with an interpreter instance, one
Rick McGuire wrote:
There is no CallProgramFromData(), but you can use NewRoutine() to
create a routine object and call thatwhich is essentially the
equivalent.
Thank you!
---rony
--
The NEW KODAK i700 Series
Analyzing the contents of the condition object in order to create the
lines ooRexx creates, if run on the command line and hitting an error.
(This is intended to be returned in form of a message string to Java, in
case a syntax error occurs on the Rexx side.)
It seems that the traceback list
This is the correct result. The traceback only includes lines back to
the point where the condition was trapped. Since your internal
routine call inherits the signal on settings from the call, the error
trap is triggered while still in the internal routine, so line 2 does
not get added to the
Rick McGuire wrote:
This is the correct result. The traceback only includes lines back to
the point where the condition was trapped. Since your internal
routine call inherits the signal on settings from the call, the error
trap is triggered while still in the internal routine, so line 2
I have a library that implements CMS/TSO Piprlines support for the PC.
I have interfaced this library to ooRexx 4.0. To accomplish this I had
to make so changes
to the 4.0 beta.
1) The interface is thru a SubCom environment. I had to modify the
subcom CommandHandler to
pass a CallContext
