comment on

I don't think these could be classified as "much better" improvements to Perl's threads, but there are some bug fixes listed in perl5160delta that target threads. Perl 5.18.0 has some additional fixes, but they appear less significant than those in 5.16.0. However, at least one of the bug fixes under 5.18.0 targets threads on Win32, which I think is one of platforms you commonly use.

If your code isn't tickling any of those bugs, fixes to thread support alone probably wouldn't be sufficient motivation to upgrade. For me, some of the Unicode support improvements found in 5.16.x were motivation enough to migrate to 5.16.

The list of modules that are broken in ways incompatible with Perl 5.18 is still significant enough, in my opinion, to wait awhile for module authors to have time to respond to the wake up call and fix their code that relies on hash order. I installed it in a perlbrew environment to see which, if any, of the modules that I frequently employ were going to be problematic, and discovered at least one that needs to have a broken test fixed.

Dave

In reply to Re^5: Why upgrade perl? by davido
in thread Why upgrade perl? by poulhs

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.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks