mirror of
https://github.com/ruby/ruby.git
synced 2022-11-09 12:17:21 -05:00
* vm.c (Thread): fix typos in overview
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@39527 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
This commit is contained in:
parent
7505436d62
commit
20514a0893
2 changed files with 8 additions and 4 deletions
|
@ -1,3 +1,7 @@
|
|||
Wed Feb 27 19:53:32 2013 Benoit Daloze <eregontp@gmail.com>
|
||||
|
||||
* vm.c (Thread): fix typos in overview
|
||||
|
||||
Wed Feb 27 13:21:00 2013 Zachary Scott <zachary@zacharyscott.net>
|
||||
|
||||
* vm.c (Thread): Typo in overview, swap setting and getting
|
||||
|
|
8
vm.c
8
vm.c
|
@ -2293,7 +2293,7 @@ Init_VM(void)
|
|||
* thr = Thread.new { ... }
|
||||
* Thread.kill(thr) # sends exit() to thr
|
||||
*
|
||||
* Alternatively, you can use the instance method #exit, or any of it's
|
||||
* Alternatively, you can use the instance method #exit, or any of its
|
||||
* aliases #kill or #terminate.
|
||||
*
|
||||
* thr.exit
|
||||
|
@ -2301,7 +2301,7 @@ Init_VM(void)
|
|||
* === Thread status
|
||||
*
|
||||
* Ruby provides a few instance methods for querying the state of a given
|
||||
* thread. To get a string with a thread's current state use #status
|
||||
* thread. To get a string with the current thread's state use #status
|
||||
*
|
||||
* thr = Thread.new { sleep }
|
||||
* thr.status # => "sleep"
|
||||
|
@ -2319,7 +2319,7 @@ Init_VM(void)
|
|||
*
|
||||
* ==== Fiber-local vs. Thread-local
|
||||
*
|
||||
* Each fiber has it's own bucket for Thread#[] storage, when you set a
|
||||
* Each fiber has its own bucket for Thread#[] storage. When you set a
|
||||
* new fiber-local it is only accessible within this Fiber. To illustrate:
|
||||
*
|
||||
* Thread.new {
|
||||
|
@ -2382,7 +2382,7 @@ Init_VM(void)
|
|||
*
|
||||
* You can also try ::pass, which attempts to pass execution to another
|
||||
* thread but is dependent on the OS whether a running thread will switch
|
||||
* or not. The same goes for #priority, which let's you hint to the thread
|
||||
* or not. The same goes for #priority, which lets you hint to the thread
|
||||
* scheduler which threads you want to take precedence when passing
|
||||
* execution. This method is also dependent on the OS and may be ignored
|
||||
* on some platforms.
|
||||
|
|
Loading…
Reference in a new issue