10/5/2023 0 Comments Activeperl 5.12 2![]() That’s not far from now at all!Īnd to make matters worse, it’s easy to do calculations today that will go well past 2038. That sounds like a lot, but that epoch value corresponds to Januat 03:14:07 UTC. If the epoch value is stored in a signed 32-bit integer, this means that you have 2,147,483,647 seconds available. Many programs stored their dates and times as seconds since the Unix epoch (JanuUTC). Well, there’s another time-related bug swiftly approaching, the Year 2038 problem. While none of the predicted catastrophes came to pass on January 1, 2000, that was in no small part because of the countless software developers who worked to prevent such catastrophes! If you’re my age, you remember the Y2K efforts of the late 90s. Let’s take a look at some of the highlights of the last six years, from 5.12 through 5.24. The simple answer is that Perl has seen quite a few new features in the past few years, ranging from little tweaks (the s///r modifier) to “this really changes all my code for the better” (subroutine signatures). How do you get from ancient Perl to modern Perl? What should you look out for? And why should you even upgrade at all? Features And Fixes Point releases are extremely safe, and we recommend always upgrading when a new point release comes out.īut if you haven’t upgraded for ages, you’re still in a difficult situation. ![]() The upshot of all this is that major Perl releases are much smaller and safer than they used to be. Jesse’s plan worked, and we’ve seen yearly releases in April (or May or June) every year from 2010’s 5.12.0 to 2016’s 5.24.0. If you want that, well, that’s one of the reasons to become an ActiveState customer! Note that when I say “support” I mean that the community of people working on Perl as a whole will work on bugs and security issues during this time frame. After that period, support ends except for critical security fixes, for which an additional year of support is provided. In between, development version point releases (5.11.0, 5.11.1) would be made once a month.Īfter a major release comes out (5.22.0, 5.24.0, etc.) there may be additional point releases (5.22.1) as needed, but only for two years after the initial release. Major releases (5.12, 5.14, etc.) would come out once a year in April. To fix all that, Perl 5 pumpking Jesse Vincent instituted a new release plan. What was an appropriate change for any release? When would changes see the light of day? It also made working on the Perl core challenging. ![]() This made upgrading Perl scary and unpredictable. For example, 5.10.1, released 20 months after 5.10, contained a number of backwards incompatibilities and quite a few new features. To make things more confusing, point releases of a given version sometimes contained large changes (including backwards incompatibilities) that we’d expect in major releases. At that point in history, major releases of Perl could take many years to come to fruition. Many organizations stopped upgrading Perl after the release of 5.8.8 or 5.10.1, about 8 to 11 years ago.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |