[前][次][番号順一覧][スレッド一覧]

ruby-changes:31017

From: ko1 <ko1@a...>
Date: Mon, 30 Sep 2013 17:29:39 +0900 (JST)
Subject: [ruby-changes:31017] ko1:r43096 (trunk): * ext/objspace/object_tracing.c: [DOC] add some nots for

ko1	2013-09-30 17:29:30 +0900 (Mon, 30 Sep 2013)

  New Revision: 43096

  http://svn.ruby-lang.org/cgi-bin/viewvc.cgi?view=rev&revision=43096

  Log:
    * ext/objspace/object_tracing.c: [DOC] add some nots for
      ObjectSpace::trace_object_allocations.

  Modified files:
    trunk/ChangeLog
    trunk/ext/objspace/object_tracing.c
Index: ChangeLog
===================================================================
--- ChangeLog	(revision 43095)
+++ ChangeLog	(revision 43096)
@@ -1,3 +1,8 @@ https://github.com/ruby/ruby/blob/trunk/ChangeLog#L1
+Mon Sep 30 17:28:39 2013  Koichi Sasada  <ko1@a...>
+
+	* ext/objspace/object_tracing.c: [DOC] add some nots for 
+	  ObjectSpace::trace_object_allocations.
+
 Mon Sep 30 16:46:58 2013  Koichi Sasada  <ko1@a...>
 
 	* ext/objspace/object_tracing.c: add new 3 methods to control tracing.
Index: ext/objspace/object_tracing.c
===================================================================
--- ext/objspace/object_tracing.c	(revision 43095)
+++ ext/objspace/object_tracing.c	(revision 43096)
@@ -245,7 +245,10 @@ trace_object_allocations_clear(VALUE sel https://github.com/ruby/ruby/blob/trunk/ext/objspace/object_tracing.c#L245
  *
  * This example has included the ObjectSpace module to make it easier to read,
  * but you can also use the
- * "<code>ObjectSpace::trace_object_allocations</code>" notation.
+ * "<code>ObjectSpace::trace_object_allocations</code>" notation (recommended).
+ *
+ * Note that this feature introduces huge performance down and huge memory
+ * consumption.
  */
 static VALUE
 trace_object_allocations(VALUE self)

--
ML: ruby-changes@q...
Info: http://www.atdot.net/~ko1/quickml/

[前][次][番号順一覧][スレッド一覧]