summaryrefslogtreecommitdiff
path: root/ext
diff options
context:
space:
mode:
Diffstat (limited to 'ext')
-rw-r--r--ext/objspace/objspace.c8
1 files changed, 2 insertions, 6 deletions
diff --git a/ext/objspace/objspace.c b/ext/objspace/objspace.c
index 2e51a3a6e5..6808352852 100644
--- a/ext/objspace/objspace.c
+++ b/ext/objspace/objspace.c
@@ -155,7 +155,6 @@ memsize_of(VALUE obj)
* T_DATA may not be correct.
*
* This method is not expected to work except C Ruby.
- * You need to <code>require 'objspace'</code> to use this method.
*/
static VALUE
@@ -222,7 +221,6 @@ total_i(void *vstart, void *vend, size_t stride, void *ptr)
* end
*
* This method is not expected to work except C Ruby.
- * You need to <code>require 'objspace'</code> to use this method.
*/
static VALUE
@@ -319,7 +317,6 @@ type2sym(enum ruby_value_type i)
* It may be changed in future.
*
* This method is not expected to work except C Ruby.
- * You need to <code>require 'objspace'</code> to use this method.
*/
static VALUE
@@ -395,7 +392,6 @@ cn_i(void *vstart, void *vend, size_t stride, void *n)
* It may be changed in future.
*
* This method is not expected to work except C Ruby.
- * You need to <code>require 'objspace'</code> to use this method.
*/
static VALUE
@@ -604,7 +600,6 @@ cto_i(void *vstart, void *vend, size_t stride, void *data)
* name, registered by rb_data_type_struct.
*
* This method is not expected to work except C Ruby.
- * You need to <code>require 'objspace'</code> to use this method.
*/
static VALUE
@@ -732,7 +727,6 @@ collect_values(st_data_t key, st_data_t value, st_data_t data)
* With this method, you can find memory leaks.
*
* This method is not expected to work except in C Ruby.
- * You need to <code>require 'objspace'</code> to use this method.
*
* Example:
* ObjectSpace.reachable_objects_from(['a', 'b', 'c'])
@@ -785,6 +779,8 @@ void Init_gc_hook(VALUE rb_mObjSpace);
* methods to get internal statistic information about
* object/memory management.
*
+ * You need to <code>require 'objspace'</code> to use this extension module.
+ *
* Generally, you *SHOULD NOT* use this library if you do not know
* about the MRI implementation. Mainly, this library is for (memory)
* profiler developers and MRI developers who need to know about MRI