On Mon, 8 Mar 2004, Flavio S. Glock wrote:
> 1- Rename module DateTime::Event::SpreadSheet
>
> Dave Rolsky wrote:
> > This looks really cool, but I don't think that's the right name for it,
> > nor am I sure that the whole spreadsheet metaphor (methods called cell,
> > etc.) is really appropriate.
>
> Rick Measham was also working on this:
> > However what I wanted to do was to be able to 'discover' that $now was
> > a part of both $this_year and $today.
> >
> > What I'm working on at the moment is not using spanset, but just a hash
> > of spans and spansets:
> > $calendar = {
> > 'sundays' => spanset of sundays,
> > 'today' => span of today,
> > 'this_year' => span of this year,
> > 'sunrise' => set of datetimes
> > }
>
> The module name choices are:
>
> DT::Event::Attributes # Dave Rolsky
> DT::Event::NamedEvents
> DT::Hash # Yitzchak Scott-Thoennes
> DT::Event::Classify # Matt Sisk
> DT::Event::Correlate
> DT::Event::Docket
> DT::Event::Named # Flavio S. Glock
> DT::Event::Spreadsheet
Well, spreadsheet actually makes a lot of sense if different cells can
refer to each other. OTOH, I think DT::Event::Named is nice and simple
too.
Also maybe DT::E::Keyed?
> 3- New method DateTime::SpanSet->span_intersection()
>
> Reinhold May wrote:
> > If I do an intersection (whether with iterator->next($span)
> > or $spanset->intersection($span) or even
> > $spanset->as_list($span)), I get a SpanSet that can have,
> > depending on where the intersection span starts and ends, a cut
> > first span and a cut last span:
> >
> > |----| |----| |----| |----| # Source SpanSet
> > |----------------| # intersection Span
> >
> > |--| |----| |--| # Resulting SpanSet
> >
> > what I actually need is a set of unmodified spans intersected by
> > that span:
> >
> > |----| |----| |----| # Wanted resulting SpanSet
I'm not sure that calling it span_intersection makes sense. How about
intersected_spans, since that's what it returns, right?
> Dave Rolsky wrote:
> > Actually, this doesn't encourage it and we _still_ need iterate() for
> > sure. We can have set_map() only be used to create a new set, and
> > iterate() only be used to alter the current set in place.
>
> Why not have _all_ methods create new sets?
That's fine with me. What do others think?
-dave
/*=======================
House Absolute Consulting
www.houseabsolute.com
=======================*/
