#49 Support a global trace

None
closed
Rick McGuire
None
none
5
2014-06-29
2005-03-01
mdlueck
No

Currently trace is turned off / reset when the
execuation moves out of scope of where trace was turned
on. In Object CUR I recently added code to every method
to check a shared object to see if trace was requested,
and if so turn on the requested trace options. This is
a rather ugly method to arrive at global trace.

Discussion

  • LesK
    LesK
    2007-11-09

    Logged In: YES
    user_id=1659105
    Originator: NO

    Sort of like the global trace available on VM!

     
  • Rick McGuire
    Rick McGuire
    2014-06-29

    • status: open --> closed
    • assigned_to: Rick McGuire
    • Pending work items: --> none
     
  • Rick McGuire
    Rick McGuire
    2014-06-29

    I'm going to close this one, since the ::OPTIONS directive allows turning on tracing within a single source file, which really addresses the scope of what you were trying to solve. A global trace that traces everything will not be added, since such a thing would not really be useful given the number of things in ooRexx that are implemented using Rexx code.

     


Anonymous


Cancel   Add attachments