hope we'll all be proud of what Perl is becoming. And ready to get back
to the keyboard for 5.12, for which, I hope, we'll not wait as long as
we waited for 5.10.
I personally believe that we can ask perl for an estimate:
#!/usr/bin/perl
use strict;
use warnings;
use Date::Parse;
use Statistics::LineFit;
my $lf=Statistics::LineFit->new;
$lf->setData([4,6,8,10], [map str2time($_), split /\n/ => <<'.EOD']);
13 Jun 1997
22 Mar 2000
18 Jul 2002
18 Dec 2007
.EOD
my ($i,$s)=$lf->coefficients;
print "Perl 5.12 estimated release date: " . localtime($i+$s*12), "\n"
+;
__END__
Of course, anyone who both sucks less is better than me at statistics, and knows perl history better than I do, could improve on this. Anyway, I get:
Perl 5.12 estimated release date: Mon Jul 5 13:00:00 2010
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|