At 10:58 PM 1/31/2001 +0100, [EMAIL PROTECTED] wrote:
>On Wed, Jan 31, 2001 at 09:53:23AM -0200, Branden wrote:
> > [EMAIL PROTECTED] wrote:
> > > > sub Time::Local::time {
> > > > return int(CORE::now());
> > > > }
> > >
> > > Why the urge to move it out of the core? Should perl6 be like Python,
> > > where you first need to do a gazillion imports before you can do anything
> > > useful? Say goodbye to quick one-liners then.
> >
> > Because with a better built-in that handles fractions of second (if that's
> > ever desired, and I guess it is), time() would be deprecated and could
> > be easily reproduced as int(now()) or anything like it. It could be in
> > a module so that anyone that still wants to use it can find it there. This
> > was suggested in RFC 48, that proposes deprecation of localtime and gmtime,
> > in favor of the new date and utcdate, and put the old ones in Time::Local.
>
>time() is a very simple call, only a few lines of code in the Perl
>source, without much overhead. It's also used quite a lot. There's
>hardly anything to gain by removing it, it will break a fair number
>of programs, and the alternative requires you to pull in a module.
>That doesn't seem a fair trade-off to me.
Pulling out or mangling time strikes me as intensely pointless, and I don't
see it happening. The socket stuff is really the only core functionality
that makes any sense to pull out, and that only from an architectural
standpoint.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
