Dave Rolsky wrote:
It has a pretty different API, in that it's new() constructor accepts
anything without validation.
I suppose it could check for extra args and call DateTime::Fat->new() if
needed.
Can we split the existing new() into validation vs. object creation and share it
between the two equally (no, I haven't looked at the source)? Thus, the
lightweight new() could validate by default, but offer a quick
no_validate => 1
option for the people creating objects out of databases (prevalidated). It may
be once that you are slinging lightweight objects around most of the time, the
performance drain due to validation won't be quite as noticible.
I think that'd be a possibility, but it'd have to pass the DateTime.pm
test suite in that case.
That's certainly where I was considering starting (with the test suite). It
might also be a good experiment to see where the performance issues really are.
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
