/ 
Perl-Review-0.04
/ Perl::Review::Policy::Modules::ProhibitUnpackagedCode

NAME

Perl::Review::Policy::Modules::ProhibitUnpackagedCode

DESCRIPTION

Conway doesn't specifically mention this, but I've come across it in my own work. In general, the first statement of any Perl module or library should be a package statement. Otherwise, all the code that comes before the package statement is getting executed in the caller's package, and you have no idea who that is. Good encapsulation and common decency require your module to keep its innards to itself.

As for scripts, most people understand that the default package is main, but it doesn't hurt to be explicit about it either. So include the package main statement at the top of your scripts too.

There are some valid reasons for not having a package statement at all. But make sure you understand them before assuming that you should do it too.

AUTHOR

Jeffrey Ryan Thalhammer <thaljef@cpan.org>

Copyright (c) 2005 Jeffrey Ryan Thalhammer. All rights reserved.

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of this license can be found in the LICENSE file included with this module.