I'm curious to know why different rules apply for arguments to methods
(rexxref p 104)
In case of method call, why the string message is not sent when
request(string) returns .nil ?
d = .directory~new
say(d) -- a Directory
.stdout~say(d) -- error argument 1 must have a string value
This works
trace ?i
...some intermediate code
r=myobj~mymeth
When I see that a result is wrong, I can rexecute the previous statement
with =
but how can I step into the called method ?
I could stop the debug, put trace ?i inside the called method and restart
the debug, but is there a more direct technique
There's no step into debugging methodadding a trace statement is
your only option. Note that you can also use the new ::OPTIONS
directives to set the default trace setting for any entire source
file.
Rick
On Sun, Sep 6, 2009 at 12:04 PM, Jean-Louis
Faucherjfaucher...@gmail.com wrote:
trace
Questions, questions, seems to be a bunch of them lately. grin
If you have an unguarded method, that then invokes another method in
the same object, does that other method also need to be unguarded?
Seems to me like it would be, but I'm not sure ...
::method handleThisStuff private
::method
Yes, each method manages its own locks on the scope variable pool. If
you want unguarded behavior all the way out, then all of the methods
need to be unguarded.
Rick
On Sun, Sep 6, 2009 at 2:27 PM, Mark Miesfeldmiesf...@gmail.com wrote:
Questions, questions, seems to be a bunch of them lately.
