kotovalexarian-likes-github/ruby--ruby
1
0
Fork 0
mirror of https://github.com/ruby/ruby.git synced 2022-11-09 12:17:21 -05:00
Code Releases Activity

* vm_trace.c (rb_tracepoint_new): fix documentation.

Browse source 
Commented by @emilsoman.



git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@50322 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
This commit is contained in:
ko1 2015-04-15 09:44:38 +00:00
parent 0e78899591
commit 3004c29afd
2 changed files with 6 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
ChangeLog
View file

@ -1,3 +1,8 @@
Wed Apr 15 18:43:43 2015 Koichi Sasada <ko1@atdot.net>
* vm_trace.c (rb_tracepoint_new): fix documentation.
Commented by @emilsoman.
Wed Apr 15 17:36:51 2015 Koichi Sasada <ko1@atdot.net> Wed Apr 15 17:36:51 2015 Koichi Sasada <ko1@atdot.net>
* vm_trace.c (rb_tracepoint_new): Add documentation for * vm_trace.c (rb_tracepoint_new): Add documentation for

2
vm_trace.c
View file

@ -1191,7 +1191,7 @@ tracepoint_new(VALUE klass, rb_thread_t *target_th, rb_event_flag_t events, void
* It is important to note that you cannot register callbacks for normal events and internal events * It is important to note that you cannot register callbacks for normal events and internal events
* simultaneously because they are different purpose. * simultaneously because they are different purpose.
* You can use any Ruby APIs (calling methods and so on) on normal event hooks. * You can use any Ruby APIs (calling methods and so on) on normal event hooks.
* However, you can not use any Ruby APIs (even object creations). * However, in internal events, you can not use any Ruby APIs (even object creations).
* This is why we can't specify internal events by TracePoint directly. * This is why we can't specify internal events by TracePoint directly.
* Limitations are MRI version specific. * Limitations are MRI version specific.
* *