ossp-pkg/pth/pth.pod 1.153 -> 1.154
--- pth.pod 2002/04/27 11:18:57 1.153
+++ pth.pod 2002/10/15 20:34:22 1.154
@@ -552,8 +552,8 @@
a thread never directly switches to another thread. A thread always
yields execution to the scheduler and the scheduler dispatches to the
next thread. So a freshly spawned thread has to be kept somewhere until
-the scheduler gets a chance to pick it up for scheduling. That is
-what the B<NEW> queue is for.
+the scheduler gets a chance to pick it up for scheduling. That is
+what the B<NEW> queue is for.
The purpose of the B<DEAD> queue is to support thread joining. When a
thread is marked to be unjoinable, it is directly kicked out of the
@@ -799,13 +799,13 @@
This sets the attribute field I<field> in I<attr> to a value
specified as an additional argument on the variable argument
list. The following attribute I<fields> and argument pairs can
-be used:
+be used:
PTH_ATTR_PRIO int
PTH_ATTR_NAME char *
PTH_ATTR_JOINABLE int
PTH_ATTR_CANCEL_STATE unsigned int
- PTH_ATTR_STACK_SIZE unsigned int
+ PTH_ATTR_STACK_SIZE unsigned int
PTH_ATTR_STACK_ADDR char *
=item int B<pth_attr_get>(pth_attr_t I<attr>, int I<field>, ...);
@@ -1644,7 +1644,7 @@
This is a variant of the 4.2BSD connect(2) function. It establishes a
connection on a socket I<s> to target specified in I<addr> and I<addrlen>.
-The difference between connect(2) and pth_connect(3) is that
+The difference between connect(2) and pth_connect(3) is that
pth_connect(3) suspends only the execution of the current thread and not the
whole process. For more details about the arguments and return code semantics
see connect(2).
|
|
