OSSP CVS Repository

ossp - Difference in ossp-pkg/pth/pth.pod versions 1.140 and 1.141
Not logged in
[Honeypot]  [Browse]  [Home]  [Login]  [Reports
[Search]  [Ticket]  [Timeline
  [History

ossp-pkg/pth/pth.pod 1.140 -> 1.141

--- pth.pod      2000/08/18 08:35:29     1.140
+++ pth.pod      2000/08/18 08:47:51     1.141
@@ -1584,26 +1584,20 @@
 
 This is a variant of the 4.3BSD usleep(3) function. It suspends the current
 threads execution until I<usec> microseconds (= I<usec>*1/1000000 sec)
-elapsed. The thread is guaranteed to not awakened before this time, but
+elapsed.  The thread is guaranteed to not awakened before this time, but
 because of the non-preemptive scheduling nature of B<Pth>, it can be awakened
-later, of course. The difference between usleep(3) and pth_usleep(3) is that
+later, of course.  The difference between usleep(3) and pth_usleep(3) is that
 that pth_usleep(3) suspends only the execution of the current thread and not
-the whole process.  The function returns the value C<0> if successful,
-otherwise the value C<-1> is returned and the global variable C<errno> is set
-to indicate the error.
+the whole process.
 
 =item unsigned int B<pth_sleep>(unsigned int I<sec>);
 
-This is a variant of the POSIX sleep(3) function. It
-suspends the current threads execution until I<sec> seconds elapsed.  The
-thread is guaranteed to not awakened before this time, but because of the
-non-preemptive scheduling nature of B<Pth>, it can be awakened later, of
-course. The difference between sleep(3) and pth_sleep(3) is that that
-pth_sleep(3) suspends only the execution of the current thread and not the
-whole process.  If the function returns because the requested time has
-elapsed, the value returned will be C<0>. If the function returns due to the
-delivery of a signal, the value returned will be the unslept amount (the
-requested time minus the time actually slept) in seconds.
+This is a variant of the POSIX sleep(3) function. It suspends the current
+threads execution until I<sec> seconds elapsed.  The thread is guaranteed to
+not awakened before this time, but because of the non-preemptive scheduling
+nature of B<Pth>, it can be awakened later, of course.  The difference between
+sleep(3) and pth_sleep(3) is that that pth_sleep(3) suspends only the
+execution of the current thread and not the whole process.
 
 =item pid_t B<pth_waitpid>(pid_t I<pid>, int *I<status>, int I<options>);
 

CVSTrac 2.0.1