someone wrote:
>
> hardly anything to gain by removing it,
> it will break a fair number of programs,
Programs will be broken anyway, even without changing time().
> 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.
> If I would think typing 'use Time::Local "time"' isn't too much to ask
> to get basic functionality, I'd be using Python.
I don't believe that's the only thing standing between you and python.
It's certainly not the only thing standing between me and python.
> Things just being there is a feature of Perl.
Yes, but things getting sucked in automatically and transparently
is also a feature of perl, or could be.
> Perl6 doesn't have to be 100% compatible with perl5,
> but that's not an invitation to break everything that can be broken.
Not changing things (for the better) in the name of not "breaking"
things is a non-starting argument. "Perl should remain Perl" (once
known as RFC 0) is bogus, because it's entirely too subjective.
Should we have said, "Perl should remain Awk"? Or do we make a better
thing?
--
John Porter
So take a pointed stick and touch Piggy's eyes
He's gonna turn and leave you a big surprise
