| Subject: | Spelling errors in pod |
Hi,
there are some little spelling errors in your pod. Here is the patch
Cheers,
Xavier
| Subject: | spelling.patch |
Description: fix a spelling mistake
Origin: vendor
Forwarded: yes
Author: gregor herrmann <gregoa@debian.org>
Reviewed-by: Xavier Guimard <x.guimard@free.fr>
Last-Update: 2013-01-04
--- a/Coro.pm
+++ b/Coro.pm
@@ -731,7 +731,7 @@
Returns true iff this Coro object is "new", i.e. has never been run
yet. Those states basically consist of only the code reference to call and
the arguments, but consumes very little other resources. New states will
-automatically get assigned a perl interpreter when they are transfered to.
+automatically get assigned a perl interpreter when they are transferred to.
=item $state->is_zombie
@@ -1234,7 +1234,7 @@
by the forks module, which gives you the (i-) threads API, just much
faster).
-Sharing data is in the i-threads model is done by transfering data
+Sharing data is in the i-threads model is done by transferring data
structures between threads using copying semantics, which is very slow -
shared data simply does not exist. Benchmarks using i-threads which are
communication-intensive show extremely bad behaviour with i-threads (in
--- a/Coro/State.pm
+++ b/Coro/State.pm
@@ -168,7 +168,7 @@
everywhere.
If the coderef is omitted this function will create a new "empty"
-thread, i.e. a thread that cannot be transfered to but can be used
+thread, i.e. a thread that cannot be transferred to but can be used
to save the current thread state in (note that this is dangerous, as no
reference is taken to ensure that the "current thread state" survives,
the caller is responsible to ensure that the cloned state does not go
@@ -237,7 +237,7 @@
Forcefully destructs the given Coro::State. While you can keep the
reference, and some memory is still allocated, the Coro::State object is
-effectively dead, destructors have been freed, it cannot be transfered to
+effectively dead, destructors have been freed, it cannot be transferred to
anymore, it's pushing up the daisies.
=item $state->call ($coderef)
--- a/README
+++ b/README
@@ -1009,7 +1009,7 @@
evidenced by the forks module, which gives you the (i-) threads API,
just much faster).
- Sharing data is in the i-threads model is done by transfering data
+ Sharing data is in the i-threads model is done by transferring data
structures between threads using copying semantics, which is very slow -
shared data simply does not exist. Benchmarks using i-threads which are
communication-intensive show extremely bad behaviour with i-threads (in