James Mastros <[EMAIL PROTECTED]> writes: > Why can't we change the meaning of time() slightly without changing to a > different function name? Yes, it will silently break some existing code, > but that's OK -- remember, 90% with traslation, 75% without. being in that > middle 15% isn't a bad thing. I think we can easily use up larry's 75%/90% 'allowance' just breaking stuff where we really have to, without breaking things for the sake of it too. Give time() an optional arg, or rename it, or anything really, but please make plain time() behave the same as before. IMHO. # s/H//; Dave.
- Re: Why shouldn't sleep(0.5) DWIM? Andreas J. Koenig
- Re: Why shouldn't sleep(0.5) DWIM? Andy Dougherty
- Re: Why shouldn't sleep(0.5) DWIM? Jarkko Hietaniemi
- 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? 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