I was looking at this from the angle of breakages, and I remember following some of the P5P threads when things were removed that caused breakages on CPAN. For modules that are high upstream on the CPAN River, patches were submitted, and for other packages, bugs were filed on RT.
Right -- all that to say, there have been some minor changes, but p5p have been quite good about testing and making fixes as they are required, in order that there's the least amount of surprise when the new version of Perl is released.
Also -- funny you mentioned study, as I was going to use that as my example function, then decided it was a little too obscure, and replaced it with split. I'm aware of it, but never had a regex complex enough to wonder if study might have helped. Also, I'm the kind of person who actually does read every line of a thousand page reference book, even if I only end up using 20% of the material. And study was used in a piece of Perl poetry I read, and I thought it was a cool keyword.
Alex / talexb / Toronto
Thanks PJ. We owe you so much. Groklaw -- RIP -- 2003 to 2013.
-
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.
|