Or are there any effects putting production code into danger?

I wouldn't say so. perl5i, which aims to be production-code material, has full autobox support.

One advantage of the "everything is an object" paradigm is the fact that namespace pollution is totally avoided. This allows to have many utility functions for each particular data structure type, without the danger of overcrowding the main namespace.

In perl5i, for instance, you can now do:

say "  this is some title.  "->trim->title_case;

# This Is Some Title.

[download]

or

my $paragraph = "Lorem Ipsum " x 90;

say $paragraph->wrap();

[download]

There are many more methods specific for arrays, hashes, code references, etc. This wouldn't be practical without this paradigm, as it would quickly pile up into having either long and awkard function names to prevent collision (hi PHP!), or avoiding having them altogether.

At first, as many people here, I was skeptical as to the usefulness of it. After playing with this for a couple of days, I found that it can indeed be quite useful, and sometimes it also reads more naturally. YMMV.

Blog

In reply to Re: What are the drawbacks of autobox? by bruno
in thread What are the drawbacks of autobox? by LanX

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


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.