Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

I'd maybe point out in the "you can break the OS" part that while the OS may include a version that has what are now known bugs, sometimes there are features that effectively depend on those because the OS counts on the bad behavior for some reason. All the more reason to wait for the system Perl to get updated with system updates.

Another pro is that if you're trying to either test someone else's code that depends on the version, or test a claimed bug (e.g. posted at PM) it's much easier to do if you're set up to switch among Perl installs at will, and can install new ones safely and cleanly with something like Perlbrew.

It's easier to upgrade to a new Perl if you don't have to do it all at once. You can install the latest and greatest, write new code with it, etc. without worrying about breaking any of your existing code and having to spend a bunch of unplanned time fixing it. This is especially useful for "intermittent" developers like me. (FWIW, I do find that Perl tends to have very good backward compatibility and can't recall the last time I ran into a conflict, unlike Ruby, which sometimes makes me crazy with incompatible dependencies.

In reply to Re: RFC: (Do Not) Modify the System Perl by bitingduck
in thread RFC: (Do Not) Modify the System Perl by MidLifeXis

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others sharing their wisdom with the Monastery: (2)
As of 2024-06-20 06:30 GMT
Find Nodes?
    Voting Booth?

    No recent polls found

    erzuuli‥ 🛈The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.