On Thu, Feb 01, 2001 at 09:00:47AM -0500, John Porter wrote: > > Uhm. NO! Remembering that $x+1 things have changed is an "added burden" > > over remembering that $x things have changed. > > Not as x approaches infinity. We are not changing an infinite number of things. > Please knock it off with the "Keep Perl Perl" non-argument. No. -- [It is] best to confuse only one issue at a time. -- K&R
- 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
- Re: Why shouldn't sleep(0.5) DWIM? James Mastros
- Re: Why shouldn't sleep(0.5) DWIM? Stephen P. Potter
- Re: Why shouldn't sleep(0.5) DWIM? Bart Lateur
- Re: Why shouldn't sleep(0.5) DWIM? Nicholas Clark