On Sat, 5 May 2001 21:19:26 +0200, Martijn van Beers said:
> On Sat, May 05, 2001 at 02:48:25PM -0400, srl wrote:
> > On 5 May 2001, Rich Bowen wrote:
> > > 1) A Date::Foo object will *always* have an internal
> > > representaton as an ICal string, no matter what you provide it
> > > when you create it.
> > Hm. I'm not so sure about this, but I guess it's the only way to
> > accomplish 2> and 3> elegantly.
>
> Do we want the internal representation to be a string?
I'm actually not sure. It means that we can store it for later reference, but
of course that does not necessitate that the internal represenration have that
format.
..
> which fits nicely inside 64 bits so you can store it as a number in
> databases and such. Maybe we can use something like this but with
> time info included, and write some XS around it. That would make
> it both more compact and probably faster.
I am not XS-aware right now, so taking this into XS would require some help
from someone else. But, yeah, that sounds fine to me, at least conceptually.
--
And everyone said, "If we only live,
We too will go to sea in a Sieve -
To the hills of the Chankly Bore!"
(The Jumblies, by Edward Lear)
