Joshua Hoblitt wrote:
> I'm planning on working with Iain and Flavio for any changes needed
> to DT::F::Builder or DT::Duration::Set (when it's written).
Ok, how about this for DT::Duration:Set:
- convert from 'duration' to 'set'
$dt_dur_set = from_du
On Fri, 4 Jul 2003, Flavio S. Glock wrote:
> Joshua Hoblitt wrote:
> > I'm planning on working with Iain and Flavio for any changes needed
> > to DT::F::Builder or DT::Duration::Set (when it's written).
>
> Ok, how about this for DT::Duration:Set:
Can you and/or Jo
Dave Rolsky wrote:
> Can you and/or Joshua explain what this would be used for?
It can be used to specify a time-set, in which you know
the time-differences but you don't know the absolute
start-time in advance.
Something like: "the store is open 08:00-12:00, 13:00-18:00".
You could add this obj
Flavio S. Glock wrote:
> Of course, this timetable could be a 2-dimensional array of durations.
> Sets are just another way to do it.
The 'add_duration' in DateTime::Set could be easily extended into:
$dt_set->add_durations( durations => @durations );
This might be a good alternative: we can s
> Of course, this will not allow for duration-recurrences.
Aren't recurrences basically a set of durations at fixed intervals? Could duration
sets mimic the DT::E::Recurrence API? Then you could iterate from a start time until
the end of the set (would have to look for some sort of flag return
That's all correct, and the implementation is
cut-and-paste DT::Set/DT::E::Recurrence code.
Dave wants to know _why_ we want this!
- Flavio S. Glock
> > Of course, this will not allow for
duration-recurrences.
>
> Aren't recurrences basically a set of durations at
fixed intervals? Could durat
On Sat, 2003-07-05 at 06:10, Dave Rolsky wrote:
> Can you and/or Joshua explain what this would be used for?
$greatest_duration = DateTime::Duration::set->new(
from_durations => [$d1, $d2, $d3]
)->max(
from => DateTime->now()
);
Also,
->min(
from => $dt
)
->median(
> That's all correct, and the implementation is
> cut-and-paste DT::Set/DT::E::Recurrence code.
Well I have it strait in my head now. :)
> Dave wants to know _why_ we want this!
ISO8601 recurring time intervals.
-J
--
On Fri, 4 Jul 2003, Joshua Hoblitt wrote:
> > That's all correct, and the implementation is
> > cut-and-paste DT::Set/DT::E::Recurrence code.
>
> Well I have it strait in my head now. :)
>
> > Dave wants to know _why_ we want this!
>
> ISO8601 recurring time intervals.
And what _are_ these, and w
Dave Rolsky <[EMAIL PROTECTED]>:
> Can you and/or Joshua explain what this would be used for?
Unbounded clocks?
Matt
> Maybe there is something fundamental we can boil
> out of DT::E::R. hmmm...
I found out a way to get a duration-set out
of DT::E::R:
$dt_set = new DT::E::R( %param ); # datetimes
$dur_set = $dt_set - $dt; # durations!
It will not work under the current implementation,
but it can be done.
Can you expand on this please?
-ben
On Sat, Jul 05, 2003 at 04:31:12AM -0400, Matt Sisk wrote:
> Dave Rolsky <[EMAIL PROTECTED]>:
> > Can you and/or Joshua explain what this would be used for?
>
>
>
> Unbounded clocks?
>
> Matt
> Can you expand on this please?
I was terming a 'clock' as anything with periodicity. An 'unbounded' clock would
be a clock without an associated epoch or starting date.
A clock without context still has characteristics and can be compared to other
clocks (for example, compare interval lengths).
On Sun, 2003-07-06 at 09:27, Matt Sisk wrote:
> I was terming a 'clock' as anything with periodicity. An 'unbounded' clock would
> be a clock without an associated epoch or starting date.
>
> A clock without context still has characteristics and can be compared to other
> clocks (for example, com
On Sat, 6 Jul 2003, Rick Measham wrote:
> On Sun, 2003-07-06 at 09:27, Matt Sisk wrote:
>
> > I was terming a 'clock' as anything with periodicity. An 'unbounded' clock would
> > be a clock without an associated epoch or starting date.
> >
> > A clock without context still has characteristics and
15 matches
Mail list logo
