I agree with my fellow monks and would tend to omit the brackets. However, I was interested to see what perlcritic might say so I tried it on this:
#!/usr/bin/env perl use strict; use warnings; use Quux; my $foo = Quux->new; $foo->bar->baz; $foo->bar()->baz; exit;
Even with --brutal it only complained about 2 items:
Code is not tidy at line 1, column 1. See page 33 of PBP. (Severity: + 1) No package-scoped "$VERSION" variable found at line 1, column 1. See +page 404 of PBP. (Severity: 2)
We can ignore the $VERSION issue. However, the complaint about tidiness is the oddity because in order to alleviate that we would have to insert whitespace before the brackets so that the line becomes
$foo->bar ()->baz;which to me looks worse, although it's clearly subjective. It doesn't moan at all about the bracketless line. Just something to bear in mind if your code has to pass perlcritic for some policy reason.
In reply to Re: To parens or not parens in chained method calls
by hippo
in thread To parens or not parens in chained method calls
by stevieb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |