From 3004c29afda80310da014d564d4ae7088c932e5b Mon Sep 17 00:00:00 2001 From: ko1 Date: Wed, 15 Apr 2015 09:44:38 +0000 Subject: * vm_trace.c (rb_tracepoint_new): fix documentation. Commented by @emilsoman. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@50322 b2dd03c8-39d4-4d8f-98ff-823fe69b080e --- ChangeLog | 5 +++++ vm_trace.c | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index aef2c6dfbe..ac1f2843d2 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +Wed Apr 15 18:43:43 2015 Koichi Sasada + + * vm_trace.c (rb_tracepoint_new): fix documentation. + Commented by @emilsoman. + Wed Apr 15 17:36:51 2015 Koichi Sasada * vm_trace.c (rb_tracepoint_new): Add documentation for diff --git a/vm_trace.c b/vm_trace.c index a186e0d364..d8df4f248b 100644 --- a/vm_trace.c +++ b/vm_trace.c @@ -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 * simultaneously because they are different purpose. * 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. * Limitations are MRI version specific. * -- cgit v1.2.3