Gil Barmwater

I feel this is a bug; i.e. the ';' terminates the clause so the 'ignored' should be part of the resource. Other directives work this way, consider the following syntactically correct code fragment: ::class dummy public; ::method gil; return yikes! ::method foo; ::method bar ::attribute one; ::attribute two

I feel this is a bug; i.e. the ';' terminates the clause so the 'ignored' should be part of the resource. Other directives work this way, consider the following syntactically correct code fragment: ::class dummy public; ::method gil; return yikes! ::method foo; ::method bar ::attribute one; ::attribute two

"show a string of candidates able to obey this order." - close but not quite :-) It's more like "return the value of the class attribute named ...". They could have been named BigLetters and SmallLetters vs. upper and lower just as well; there isn't any correspondence between the "upper"/"lower" instance methods and the "upper"/"lower" class attributes other than they are spelled the same. HTH

OK, fair enough. But I still find it "surprising" that the determination of the routine and method objects to be traced under "::options trace" is made when the directive is processed and not at run time.

I found it interesting that you found that no code changes were required, just creating a new method object from the same source would do the trick. I'm guessing the processing of the ::options trace directive must build a "list" of method objects to be traced and when one replaces or adds one (or more) of them with new objects, they will not be on the already created "list" and therefore not get traced. Good to know!

Glad it was helpful!

Well, you have "discovered" the essence of what I did for that presentation 10 years ago. I am going to send you the PDF off-list so you can compare what I did with your proof of concept. While my program was concerned with adding trace statements to methods prior to their execution, the same approach could add a "call trace <whatever>" to suppress tracing in selective methods. I hope you can make use of the code in some form.</whatever>

At the 2014 Symposium I did a presentation that addressed this topic. René recently asked me to update the documentation for the purpose of publishing the RexxLA Symposium proceedings. Here is the opening section of that document. ooRexx Tracing through Metaprogramming A recent discussion on the RexxLA list regarding the lack of a "global trace" capability in ooRexx led to an analysis of tracing in an object oriented environment. Due to encapsulation, each method of a class begins execution with...