[ruby-core:40569] [ruby-trunk - Feature #5528][Open] OO API for tracing

[ruby-core:40569] [ruby-trunk - Feature #5528][Open] OO API for tracing

[Thomas Sawyer]

Issue #5528 has been reported by Thomas Sawyer.

----------------------------------------
Feature #5528: OO API for tracing
http://redmine.ruby-lang.org/issues/5528

Author: Thomas Sawyer
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 2.0


It would be nice to see a better API for "set_trace_func" functionality.

I wrote a fairly simple library to do this some time ago called <a href="https://github.com/rubyworks/tracepoint>TracePoint</a>. One of the significant advantages of TracePoint is that it allows for multiple traces to be defined without interfering others and they can even be given names to activate and deactivate them independently.

It would be nice to see something like this is Ruby 2.0, it would have the a number of advantages:

* Object-oriented - a tracepoint is an object, not just an array of arguments.
* Connescence - the tracepoint methods give tangible names to the properties that are traced.
* More robust - currently one use of set_trace_func will clobber another.

And probably others beside.


-- 
http://redmine.ruby-lang.org

[ruby-core:49503] [ruby-trunk - Feature #5528] OO API for tracing

[boris_stitnicky (Boris Stitnicky)]

Issue #5528 has been updated by boris_stitnicky (Boris Stitnicky).


I think that so few people respond to this because they are not users of Tracepoint :-)
----------------------------------------
Feature #5528: OO API for tracing
https://bugs.ruby-lang.org/issues/5528#change-33035

Author: trans (Thomas Sawyer)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: Next Major


It would be nice to see a better API for "set_trace_func" functionality.

I wrote a fairly simple library to do this some time ago called <a href="https://github.com/rubyworks/tracepoint>TracePoint</a>. One of the significant advantages of TracePoint is that it allows for multiple traces to be defined without interfering others and they can even be given names to activate and deactivate them independently.

It would be nice to see something like this is Ruby 2.0, it would have the a number of advantages:

* Object-oriented - a tracepoint is an object, not just an array of arguments.
* Connescence - the tracepoint methods give tangible names to the properties that are traced.
* More robust - currently one use of set_trace_func will clobber another.

And probably others beside.


-- 
http://bugs.ruby-lang.org/

[ruby-core:52658] [ruby-trunk - Feature #5528][Closed] OO API for tracing

[ko1 (Koichi Sasada)]

Issue #5528 has been updated by ko1 (Koichi Sasada).

Category set to core
Status changed from Open to Closed
Assignee set to ko1 (Koichi Sasada)
Target version changed from Next Major to 2.0.0

TracePoint was introduced.

----------------------------------------
Feature #5528: OO API for tracing
https://bugs.ruby-lang.org/issues/5528#change-36744

Author: trans (Thomas Sawyer)
Status: Closed
Priority: Normal
Assignee: ko1 (Koichi Sasada)
Category: core
Target version: 2.0.0


It would be nice to see a better API for "set_trace_func" functionality.

I wrote a fairly simple library to do this some time ago called <a href="https://github.com/rubyworks/tracepoint>TracePoint</a>. One of the significant advantages of TracePoint is that it allows for multiple traces to be defined without interfering others and they can even be given names to activate and deactivate them independently.

It would be nice to see something like this is Ruby 2.0, it would have the a number of advantages:

* Object-oriented - a tracepoint is an object, not just an array of arguments.
* Connescence - the tracepoint methods give tangible names to the properties that are traced.
* More robust - currently one use of set_trace_func will clobber another.

And probably others beside.


-- 
http://bugs.ruby-lang.org/