Branden wrote:
Actually, with event loops and threading issues, probably things like
the perl built-ins sleep and alarm won't ever be passed to the syscalls
sleep(3) and alarm(3).
Sleep isn't usually a syscall -- it's often a library routine that sets
an alarm and blocks or uses some other
Bart Lateur wrote:
What if we take the ordinary sleep() for the largest part of the
sleeping time (no busy wait), and the 4 argument select for the
remainder, i.e. subsecond?
You're trying to solve a problem that doesn't exist.
Sleep doesn't have the signal delivery problems that alarm has,
