On Tue, 18 Feb 2003 [EMAIL PROTECTED] wrote:
> First I just want to confirm that DateTime does not support fractional
> seconds? Its a little used part of the spec,so I hardly think its a big
> deal, but it would be nice to support if possible.
Not yet. I do want to support sub-seconds resolutions, but feedback from
people on the list and from documents I've been reading seems to go back
and forth between just making seconds a floating point number and having
an explicit sub-second (nano/milli/zetto/groucho-seconds) slot in the
object.
> W3CDTf doesn't have any concept of a duration, so I left the
> parse_duration(), and format_duration() methods out of the class, is this
> allowed by the Format API? (understanding that formats are still an alpha
> feature)
Absolutely. The API will basically work like this, I think:
parse_foo - where foo is datetime, duration, interval, recurrence
format_foo - same deal
and the values of foo are those values that make sense for the format.
Ical happens to have both a datetime and duration format (and recurrences
as well). The DateTime::Format::Common module (or maybe
DateTime::Parse::Common, since it'll only do parsing), which will be like
Graham Barr's Date::Parse, will probably just implement parse_datetime.
> Any thoughts on creating a Date::Format base class? I imagine it would be
> empty exception for some minimal documentation of the API. (or you could
> stick in methods like parse_format { die "Must be overriden"; } but that
> makes it impossible to use can() )
I'm not sure how much value there is in that. A simple API document might
be just as useful.
> Are you interested in having this (and this sort of thing) checked into
> the perl-date-time project on Sourceforge, or maintained separately?
If you want to add it to the perl-date-time repository, that's fine with
me, as long as you can live with the dev standards I'm trying to impose
(which has been easy so far since I've written most of the code ;) This
is documented under docs/development-standards.pod in the repository.
It's nothing too draconian, just an attempt to ensure certain
documentation standards, mostly (and that we all use the same license).
-dave
/*=======================
House Absolute Consulting
www.houseabsolute.com
=======================*/
