summaryrefslogtreecommitdiff
path: root/doc/extension.rdoc
diff options
context:
space:
mode:
authorsvn <svn@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2015-04-14 23:26:01 +0000
committersvn <svn@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2015-04-14 23:26:01 +0000
commit14ec77d1793767fb00cdf2f945ec7e5d7a1ae8bc (patch)
tree3033602c828337c1f5971ebe84e8160d9ddf756c /doc/extension.rdoc
parent98544c372d948717de22afc86d162e411f1fb5f1 (diff)
* remove trailing spaces.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@50319 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'doc/extension.rdoc')
-rw-r--r--doc/extension.rdoc8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/extension.rdoc b/doc/extension.rdoc
index eddbf4589b..0cb1d005a3 100644
--- a/doc/extension.rdoc
+++ b/doc/extension.rdoc
@@ -670,7 +670,7 @@ to be valid as a C or Ruby identifier.
These dmark / dfree functions are invoked during GC execution. No
object allocations are allowed during it, so do not allocate ruby
objects inside them.
-
+
dmark is a function to mark Ruby objects referred from your struct.
It must mark all references from your struct with rb_gc_mark or
its family if your struct keeps such references.
@@ -688,7 +688,7 @@ But it is still recommended to avoid 0.
You have to fill reserved and parent with 0.
You can fill "data" with an arbitrary value for your use.
-Ruby does nothing with the member.
+Ruby does nothing with the member.
flags is a bitwise-OR of the following flag values.
Since they require deep understanding of garbage collector in Ruby,
@@ -696,7 +696,7 @@ you can just set 0 to flags if you are not sure.
RUBY_TYPED_FREE_IMMEDIATELY ::
- This flag makes the garbage collector immediately invoke dfree()
+ This flag makes the garbage collector immediately invoke dfree()
during GC when it need to free your struct.
You can specify this flag if the dfree never unlocks Ruby's
internal lock (GVL).
@@ -709,7 +709,7 @@ RUBY_TYPED_WB_PROTECTED ::
It shows that implementation of the object supports write barriers.
If this flag is set, Ruby is better able to do garbage collection
of the object.
-
+
When it is set, however, you are responsible for putting write
barriers in all implementations of methods of that object as
appropriate. Otherwise Ruby might crash while running.