--- pth.pod 2002/11/05 19:39:09 1.160
+++ pth.pod 2002/11/08 16:05:55 1.161
@@ -2267,9 +2267,9 @@
building B<Pth> with C<--enable-syscall-soft>. This then triggers some
C<#define>'s in the C<pth.h> header which map for instance read(3) to
pth_read(3), etc. Currently the following functions are mapped: fork(2),
-sleep(3), sigwait(3), waitpid(2), system(3), select(2), poll(2),
-connect(2), accept(2), read(2), write(2), recv(2), send(2), recvfrom(2),
-sendto(2).
+nanosleep(3), usleep(3), sleep(3), sigwait(3), waitpid(2), system(3),
+select(2), poll(2), connect(2), accept(2), read(2), write(2), recv(2),
+send(2), recvfrom(2), sendto(2).
The drawback of this approach is just that really all source files
of the application where these function calls occur have to include
@@ -2284,8 +2284,8 @@
C<--enable-syscall-hard>. This then builds wrapper functions (for instances
read(3)) into the B<Pth> library which internally call the real B<Pth>
replacement functions (pth_read(3)). Currently the following functions
-are mapped: fork(2), sleep(3), waitpid(2), system(3), select(2),
-poll(2), connect(2), accept(2), read(2), write(2).
+are mapped: fork(2), nanosleep(3), usleep(3), sleep(3), waitpid(2),
+system(3), select(2), poll(2), connect(2), accept(2), read(2), write(2).
The drawback of this approach is that it depends on syscall(2) interface
and prototype conflicts can occur while building the wrapper functions
|
