Well, you could read perldelta, and keep tracks of the reported bugs on perlbug, but that doesn't mean you detect
all things that break your programs.
But there are things you can do. First is to have a testing
environment, and a solid test suite. This hopefully unearth
things that break. But testing only determines breakage, it
doesn't resolve them.
A better approach is to have each application (or set of applications) carry its own version of Perl. That is, you
package an appropriate run-time environment of perl with
your application. Then, if one application needs a newer
version of Perl, no other application will break. Installing
newer versions of modules won't break other applications.
One can easily have different 'types' (64-bit ints, threads, dynamic library) of perl as well this way.
Abigail
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.