Mostly it makes it difficult to catch errors if those methods fail.

But not any more difficult that catching an error in *any* chaining call. The OP had no problem with: 
my $label_formatting = $button->child->font_style;

[download]
but if there's an error in the child method, it'll be as hard to catch as in: 
$window->title('foo')->border(20);

[download]

And if your methods just throw exceptions on errors, you can just wrap it all in an eval: 

eval {$window->title('foo')->border(20)};
if ($@) {...do something...}

[download]
If that isn't good enough for you, because you need fine grained control on catching errors, you can always write: 
eval {$window->title('foo')};
if ($@) {....}
else {eval {$window->border(20)}
      if ($@) {....}}

[download]
The point is that mutators returning $self allow for either style. Chaining for those who want it, and fine control for those who want that.

Returning the argument passed in is IMO not very useful. The OP mentioned "that's how = does it - it allows you to write $foo = $bar = $baz;. That's true, but the OO equivalent would be: 

$obj->foo($obj->bar($baz))

[download]
which, IMO, gets unwieldy very quickly and isn't very readable either. I also have seldomly any use for that.

In reply to Re^4: Mutator chaining considered harmful by Anonymous Monk
in thread Mutator chaining considered harmful by Aristotle

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.