> Just the format_datetime function when it comes to the value which is
> assigned to the time_zone attribue.Â It's already an attribute of the
I simply /do not/ believe you understand the difference between being
1:30 "read-in the context of" America/Chicago, and "converting it with
date-math" to the timezone of America/Chicago. The constructor
argument has /nothing at all/ to do with what your wanting (date-math
>> Here is better API idea, why not just make the hash ref to
>> format_datetime, a huge method wrapper!!!!
> Taken to the point of absurdity.
But why not? If your goal is simply to provide a convenience wrapper
that is capable of doing the date-math through DateTime, then why not
permit you to say, add => '1 hour', to the current time, to "format"
the time for a clock that is moving one hour too slow? I agree it is
rather absurd and silly, but I'm not seeing why it is /more/ silly.
Maybe it would be better if for your understanding you read all of
these arguments as implicitly suffixed with
"as_used_in_the_constructor_to_DateTime", so you don't confuse the
DT::Format::* with something that can or should manipulate the
supplied DateTime in the call to parse_datetime.
System Lord of the Internets