Dan Sugalski wrote: > At 11:57 PM 1/31/2001 +0100, [EMAIL PROTECTED] wrote: > > On Wed, Jan 31, 2001 at 05:35:03PM -0500, Michael G Schwern wrote: > > > grossly UNIX specific things like getpwnam's [can be pulled] > > > > But why? What is it going to buy you? > > Not that much. More than anything else the ability to deal with them > externally for non-unix platforms. So on Unix-like platforms getpwnam is pre-loaded and on all the others it's auto-loaded (a Unix compatiblity module or something). If it's faster pre-loading a module than telling the auto-loader about it, we should pre-load. Speed always wins over size in perl. I might be off base, but there seems to be a movement to take Unix out of Perl. Sometimes I'm not sure if we're arguing about "time() returns an int" or "time() looks like Unix so it has to change." IMHO I'd like to see more Unix in Perl, not less. (We can do better than the C API though.) - Ken
- 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
- 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? abigail
- Re: Why shouldn't sleep(0.5) DWIM? John Porter