Perl::Critic::Policy::Subroutines::ProhibitBuiltinHomonyms(3pm)

Perl::Critic::Policy::Subroutines::ProhibitBuiltinHomonyms3pm

Don't declare your own "open" function.

Affiliation

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

Overview

Common sense dictates that you shouldn't declare subroutines with the same name as one of Perl's built-in functions or keywords. See perlfunc for a list of built-in functions; see perlsyn for keywords.

  sub open {}    #not ok
  sub exit {}    #not ok
  sub print {}   #not ok
  sub foreach {} #not ok
  sub if {}      #not ok
  #You get the idea...

Exceptions are made for "BEGIN", "END", "INIT" and "CHECK" blocks, as well as "AUTOLOAD", "DESTROY", and "import" subroutines.

Configuration

You can configure additional builtin homonyms to accept by specifying them in a space-delimited list to the "allow" option:

    [Subroutines::ProhibitBuiltinHomonyms]
    allow = default index

These are added to the default list of exemptions from this policy. So the above allows "sub default {}" and "sub index {}".

Caveats

It is reasonable to declare an object method with the same name as a Perl built-in function, since they are easily distinguished from each other. However, at this time, Perl::Critic cannot tell whether a subroutine is static or an object method.

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

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.