ooRexx 4.2.0 introduces two new monitor objects, .debuginput and .traceoutput.
In the current beta their destination object is .nil, hence messages directed
at them usually raise
an unknown method condition, like:
F:\work\svn\bsf4oorexx\trunk\bsf4oorexx\install>rexxtry
REXX-ooRexx_4.2.0(MT)_32-bit 6.04 8 Dec 2013
rexxtry.rex lets you interactively try REXX statements.
Each string is executed when you hit Enter.
Enter 'call tell' for a description of the features.
Go on - try a few... Enter 'exit' to end.
call rgf_util2.rex
........................................... rexxtry.rex on WindowsNT
say .traceoutput~destination
The NIL object
........................................... rexxtry.rex on WindowsNT
.traceoutput~say("hi")
Oooops ! ... try again. Object method not found
Object "The NIL object" does not understand
message "SAY"
rc = 97.1 ................................. rexxtry.rex on WindowsNT
say .debuginput~destination
The NIL object
........................................... rexxtry.rex on WindowsNT
a=.debuginput~linein
Oooops ! ... try again. Object method not found
Object "The NIL object" does not understand
message "LINEIN"
rc = 97.1 ................................. rexxtry.rex on WindowsNT
Was the intention perhaps to have .debuginput use .stdin as its default
destination, and
.traceoutput use .stderr as its default destination?
---rony
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
