<?xml version="1.0" encoding="windows-1252"?>
<node id="478641" title="Re^2: The Perl Crackpot Index" created="2005-07-27 11:29:55" updated="2005-08-13 07:39:18">
<type id="11">
note</type>
<author id="37858">
autarch</author>
<data>
<field name="doctext">
&lt;p&gt;&lt;i&gt;The functionality provided by DateTime absolutely should be in core.&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
Eek, no!  The DT stuff needs to keep up with leap second and time zone change announcements, so it needs its own release schedule.  We'd have to figure out a way to release data packages separately from what's in the core.
&lt;/p&gt;

&lt;p&gt;
Of course, in theory, I can see why this should be in the core, just because it's the kind of low-level data type that you want for programming.
&lt;/p&gt;

&lt;p&gt;
But given how easy CPAN is to use, is it really a big barrier?  I think the big problem, as usual, is that there's lots of similar stuff to wade through.  Fortunately, DateTime seems to have enough of a following these days that every time there's a datetime programming question, at least one respondent says "use DateTime", so the word is out.
&lt;/p&gt;</field>
<field name="root_node">
478175</field>
<field name="parent_node">
478573</field>
</data>
</node>
