View on
MetaCPAN is shutting down
For details read Perl NOC. After June 25th this page will redirect to
Jeffrey Ryan Thalhammer > Perl-Critic-1.119 > Perl::Critic::Policy::Modules::RequireFilenameMatchesPackage



Annotate this POD



New  61
Open  120
Stalled  4
View/Report Bugs
Module Version: 1.119   Source   Latest Release: Perl-Critic-1.132


Perl::Critic::Policy::Modules::RequireFilenameMatchesPackage - Package declaration must match filename.


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


The package declaration should always match the name of the file that contains it. For example, package Foo::Bar; should be in a file called This makes it easier for developers to figure out which file a symbol comes from when they see it in your code. For instance, when you see Foo::Bar->new(), you should be able to find the class definition for a Foo::Bar in a file called

Therefore, this Policy requires the last component of the first package name declared in the file to match the physical filename. Or if #line directives are used, then it must match the logical filename defined by the prevailing #line directive at the point of the package declaration. Here are some examples:

  # Any of the following in file "Foo/Bar/":
  package Foo::Bar::Baz;     # ok
  package Baz;               # ok
  package Nuts;              # not ok (doesn't match physical filename)

  # using #line directives in file "Foo/Bar/":
  #line 1
  package Nuts;             # ok
  package Baz;              # not ok (contradicts #line directive)

If the file is not deemed to be a module, then this Policy does not apply. Also, if the first package namespace found in the file is "main" then this Policy does not apply.


This Policy is not configurable except for the standard options.


Chris Dolan <>


Copyright (c) 2006-2011 Chris Dolan.

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

syntax highlighting: