On Friday, January 24, 2003, at 03:14 PM, Dave Rolsky wrote:
On Fri, 24 Jan 2003, Bruce Van Allen wrote:
be updatable at all. It appeared to me that consensus formed to have
objects static, and updating would be done via cloning:
I wouldn't say there was consensus ;)
So many threads and sub-t
So I'm hacking away at time zone code and getting darn close to producing
something usable, dare I even say elegant? We'll see on both counts, I
suppose ;)
Anyway, I've been working with the raw Olson DB the last couple days, and
I've produced a parser that can read its "rules", "zones", "links"
On Fri, 24 Jan 2003, Tim Bunce wrote:
> Would someone do me the great favour of summarizing some things for me?
>
> Just the Goals and Design Principles would be great, an outline of
> the API(s) would be a bonus.
>
> I'm particularly interested in:
> Basic object API (there is going to be a
On Fri, 24 Jan 2003, Bruce Van Allen wrote:
> Some of the discussion was about whether or not DateTime objects should
> be updatable at all. It appeared to me that consensus formed to have
> objects static, and updating would be done via cloning:
>
>$dt = DateTime->new( year => 2001, month =>
On Fri, 24 Jan 2003, Clayton L. Scott wrote:
> So if I want to use Sunday as the first day of the week every will
> method I use will have "sunday" in it? What if for some business reason
> I decide that it's easier to do my calculations if Wednesday is the first
> day of the week?
>
> How about:
On Fri, 24 Jan 2003, Dave Rolsky wrote:
> On Fri, 24 Jan 2003, Peter J. Acklam wrote:
> > In relation to week numbers and day of week numbers, there are
> > at least four parameters that must be customizable:
> >
> >1) What is the first day of a week (Sunday, Monday, ...)?
>
> I just need met
On Fri, 24 Jan 2003, Peter J. Acklam wrote:
> I believe this thread proves that what is considered the first day
> of the week must be customizable. If it isn't, then someone
> (perhaps not someone on this mailing list, but someone) will be
> dissatisfied and consider the "DateTime" modules usele
On Friday, January 24, 2003, at 03:45 AM, Rich Bowen wrote:
Someone who is watching the list more closely than I appear to be
pointed out to me that some discussion had occurred about get/set
attribute methods. I can't find that discussion, and don't feel like
[snip]
Now, if this matter neve
Would someone do me the great favour of summarizing some things for me?
Just the Goals and Design Principles would be great, an outline of
the API(s) would be a bonus.
I'm particularly interested in:
Basic object API (there is going to be an object right?)
Extensibility (through s
Someone who is watching the list more closely than I appear to be
pointed out to me that some discussion had occurred about get/set
attribute methods. I can't find that discussion, and don't feel like
searching for it at this time of the morning, and before coffee to boot.
Anyways, apparently some
On Fri, 24 Jan 2003, Peter J. Acklam wrote:
> [EMAIL PROTECTED] (Dave Rolsky) wrote:
>
> > Ok, having accepted the fact that day of week numbering will be
> > 1-7, now we get to argue about which day is #1.
> >
> > Time::Piece (interface by Larry Wall) says Sunday, as does
> > localtime, which com
[EMAIL PROTECTED] (Dave Rolsky) wrote:
> Ok, having accepted the fact that day of week numbering will be
> 1-7, now we get to argue about which day is #1.
>
> Time::Piece (interface by Larry Wall) says Sunday, as does
> localtime, which comes from C's localtime function
>
> Date::Calc says Monday,
12 matches
Mail list logo
