On Wed, Jan 31, 2001 at 05:35:03PM -0500, Michael G Schwern wrote: > On Wed, Jan 31, 2001 at 05:23:43PM -0500, Dan Sugalski wrote: > > Pulling out or mangling time strikes me as intensely pointless, and I don't > > see it happening. The socket stuff is really the only core functionality > > that makes any sense to pull out, and that only from an architectural > > standpoint. > > Perhaps some of the more grossly UNIX specific things like getpwnam's > extended family and the SysV IPC stuff? But why? What is it going to buy you? Abigail
- Re: Why shouldn't sleep(0.5) DWIM? James Mastros
- Re: Why shouldn't sleep(0.5) DWIM? Jarkko Hietaniemi
- Re: Why shouldn't sleep(0.5) DWIM? Bart Lateur
- Re: Why shouldn't sleep(0.5) DWIM? Jarkko Hietaniemi
- Re: Why shouldn't sleep(0.5) DWIM? Branden
- Re: Why shouldn't sleep(0.5) DWIM? abigail
- Re: Why shouldn't sleep(0.5) DWIM? Dan Sugalski
- Re: Why shouldn't sleep(0.5) DWIM? Michael G Schwern
- Re: Why shouldn't sleep(0.5) DWIM? Jarkko Hietaniemi
- Re: Why shouldn't sleep(0.5) DWIM? Michael G Schwern
- Re: Why shouldn't sleep(0.5) DWIM? abigail
- Re: Why shouldn't sleep(0.5) DWIM? Simon Cozens
- Re: Why shouldn't sleep(0.5) DWIM? Andy Dougherty
- Re: Why shouldn't sleep(0.5) DWIM? Dan Sugalski
- Re: Why shouldn't sleep(0.5) DWIM? Ken Fox
- Re: Why shouldn't sleep(0.5) DWIM? John Porter
- Re: Why shouldn't sleep(0.5) DWIM? Simon Cozens
- Re: Why shouldn't sleep(0.5) DWIM? John Porter
- Re: Why shouldn't sleep(0.5) DWIM? Simon Cozens
- Re: Why shouldn't sleep(0.5) DWIM? Nicholas Clark
- Re: Why shouldn't sleep(0.5) DWIM? David Grove