parse_datetime and format_datetime
Just out of curiousity...why the '_datetime' suffix on these methods? Isn't that redundant? Or was it assuming that these methods might be showing up in classes outside of the DateTime namespace? And speaking of brevity...the 0.18 docs for DateTime say that 'time_zone_long_name' is short for $dt-tz-name. I see no evidence of a 'tz' method, though it'd be nice to have around, along with 'tz_name', etc. Thanks, Matt
Re: parse_datetime and format_datetime
Just out of curiousity...why the '_datetime' suffix on these methods? Isn't that redundant? Or was it assuming that these methods might be showing up in classes outside of the DateTime namespace? To differentiate from: _date, _time, _span, etc. And speaking of brevity...the 0.18 docs for DateTime say that 'time_zone_long_name' is short for $dt-tz-name. I see no evidence of a 'tz' method, though it'd be nice to have around, along with 'tz_name', etc. 'tz' is a key in the blessed hash of a DateTime object. The docs should say $dt-time_zone-name. -J --
Re: parse_datetime and format_datetime
On Wed, 5 Nov 2003, Matt Sisk wrote: Just out of curiousity...why the '_datetime' suffix on these methods? Isn't that redundant? Or was it assuming that these methods might be showing up in classes outside of the DateTime namespace? Because we can parse and format things that aren'ts datetimes, like dates, durations, spans, etc. And speaking of brevity...the 0.18 docs for DateTime say that 'time_zone_long_name' is short for $dt-tz-name. I see no evidence of a 'tz' method, though it'd be nice to have around, along with 'tz_name', etc. That should say short for $dt-time_zone-long_name. I'm not that big on brevity, sorry ;) -dave /*=== House Absolute Consulting www.houseabsolute.com ===*/
