On Wed, Jan 31, 2001 at 05:51:27PM -0500, John Porter wrote: > > you *don't* need to remember > > you are programming in perl5 or perl6, and get the same functionality. > > But you need to remember it anyway, so remembering it for time() is > no added burden. Uhm. NO! Remembering that $x+1 things have changed is an "added burden" over remembering that $x things have changed. > "Perl should remain Perl" (once known as RFC 0) is bogus If you want things that *aren't* Perl, you know exactly where to find them. -- I see ADA as a larger threat than communism at this point in time -- Ted Holden
- Re: Why shouldn't sleep(0.5) DWIM? Jarkko Hietaniemi
- Re: Why shouldn't sleep(0.5) DWIM? Casey R. Tweten
- Re: Why shouldn't sleep(0.5) DWIM? Andy Dougherty
- 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? David Mitchell
- 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? abigail
- 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? John Porter
- Re: Why shouldn't sleep(0.5) DWIM? abigail
- Re: Why shouldn't sleep(0.5) DWIM? Stephen P. Potter
- Re: Why shouldn't sleep(0.5) DWIM? Dan Sugalski
- Re: Why shouldn't sleep(0.5) DWIM? David Cantrell
- Re: Why shouldn't sleep(0.5) DWIM? nick
- Re: Why shouldn't sleep(0.5) DWIM? Uri Guttman
- Re: Why shouldn't sleep(0.5) DWIM? Dan Sugalski
- Re: Why shouldn't sleep(0.5) DWIM? Jarkko Hietaniemi