Perl::Critic::Policy::CodeLayout::ProhibitParensWithBuiltins(3pm)

Perl::Critic::Policy::CodeLayout::ProhibitParensWithBuiltins3pm

Write "open $handle, $path" instead of "open($handle, $path)".

Affiliation

This Policy is part of the core Perl::Critic distribution.

Overview

Conway suggests that all built-in functions be called without parentheses around the argument list. This reduces visual clutter and disambiguates built-in functions from user functions. Exceptions are made for "my", "local", and "our" which require parentheses when called with multiple arguments.

    open($handle, '>', $filename); #not ok
    open $handle, '>', $filename;  #ok
    split(/$pattern/, @list); #not ok
    split /$pattern/, @list;  #ok

Configuration

This Policy is not configurable except for the standard options.

Notes

Coding with parentheses can sometimes lead to verbose and awkward constructs, so I think the intent of Conway's guideline is to remove only the unnecessary parentheses. This policy makes exceptions for some common situations where parentheses are usually required. However, you may find other situations where the parentheses are necessary to enforce precedence, but they cause still violations. In those cases, consider using the '## no critic' comments to silence Perl::Critic.

Releases

10 releases since Debian 5.0 (Lenny); the text changed 9 times.

  1. 5.0
  2. 6.0
  3. 7
  4. 8
  5. 9
  6. 10
  7. 11
  8. 12
  9. 13
  10. Arch

Bugs

Some builtin functions (particularly those that take a variable number of scalar arguments) should probably get parentheses. This policy should be enhanced to allow the user to specify a list of builtins that are exempt from the policy.

Author

Jeffrey Ryan Thalhammer <[email protected]>

From perl-perl-critic 1.156-3 in Arch Linux 2026-11-01. Parsed by carta from the page's man source.