Lightning flashed, thunder crashed and Nathan Wiger <[EMAIL PROTECTED]> whisper
ed:
| But the big problem is that there's a lot of stuff that's based off of
| time() right now, like stat(), lstat(), etc, etc. When you think of the
| cascading effects of changing Perl's timekeeping it gets really, really
| sticky.
Most of those don't deal with subsecond time anyway, from the perspective
that (l?stat) uses what is recorded in the filesystem inode.
| If the internal timekeeping were changed, one thing that's apparent from
| the discussions is that there would *have* to be a core way of providing
| exactly what time() does currently or lots of stuff would break really
| badly. Someone can certainly chime in if they see an easy way around
| this, but as I recall there was little disagreement on this point.
Changing sleep/alarm doesn't have to involve changing perl's internal
timekeeping. sleep/alarm are just wrappers around the C library
sleep/alarm. It should be trivial to make the wrapper recognize when a
float is passed as the argument and switch to usleep (or setitimer or
whatever) when that is found.
-spp
