Typos in POD that I spotted during FAQ development:
1) DateTime::Format::Strptime: "This method is synonymous with
DateTime's strptime method."
2) DateTime: "DateTime does not if second values greater than 59 are
valid based on current leap seconds, and invalid values simply
cause an over-flow."
Questions that came up in the FAQ development (you can also see these
in the FAQ in the correct context if you search for QUESTION):
1) Is it worthwhile to add an optional resolution argument to compare
to allow easier usage? (There was discussion, but I don't think we
came down anywhere)
2) What is the overlap between DateTime::Format::Builder and
DateTime::Format::Strptime? Which is preferred?
3) QUESTION How do you print non 0 or space padded years and months?
[in strftime]
4) Wasn't this [the DateTime constructor croaking on bad dates] going
to be overridable?
5) What happened to the module that was going to handle guessing? [at
short timezone names]
6) Is there something equivalent for two days from the end of the
month? Should there be? Perhaps the flag should say whether the
start or end of the month offset is what matters... [In
DateTime::Duration]
7) Do Sets constructed from explicit dates always get sorted?
8) Should DateTime::Set have a way to add an more explicit dates
without having to make a new set and union it in?
9) Do we need a DateTime::Set clone method (ditto span, etc.)?
10) Did we ever work out how to attatch information to a date from a
set? [I remember a proposal floating about, I will have to look at
the archives]
11) Are we going to return an object for +/-inf or will it always be a
string? [I remember some discussion here, how did it turn out?]
12) Is that true about the SpanSet? If so the docs are wrong. [What
does DateTime::Set->complement() (unary) return, a Set or a
SpanSet, if a Set, what does it mean (the returned type is
currently a Set, but the values are odd]
13) How do I set a time zone on a set? (and span and spanset)
There are some other questions about alternate implementations and
business logic that I need to think about (unless someone else has any
bright ideas).
Thanks,
-ben
