> Okay, so maybe a new constructor then? DateTime->localtime()? Getting
> the current local time seems more common than, say, constructing a
> DateTime object from a day of the year, IMO :)
We have enough constructors as it is. I could be talked into:
DateTime->now( time_zone => 'local' );
But that would add extra overhead on every call to now();
Whats wrong with:
DateTime->now->set_time_zone( 'local' );
or
sub here_now { DateTime->now->set_time_zone( 'local' ) }
?
If your going to insist on another constructor you could write it as a decorator with
our new plug-in architecture. :)
-J
--
