The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.
 / 
Perl-Critic-1.06
River stage three • 133 direct dependents • 408 total dependents
130 ++
/ Perl::Critic::Policy::Modules::RequireVersionVar

NAME

Perl::Critic::Policy::Modules::RequireVersionVar

DESCRIPTION

Every Perl file (modules, libraries, and programs) should have a $VERSION variable. The $VERSION allows clients to insist on a particular revision of your file like this:

  use SomeModule 2.4;  #Only loads version 2.4

This Policy scans your file for any package variable named $VERSION. I'm assuming that you are using strict, so you'll have to declare it like one of these:

  our $VERSION = 1.061;
  $MyPackage::VERSION = 1.061;
  use vars qw($VERSION);

A common practice is to use the $Revision: 1709 $ keyword to automatically define the $VERSION variable like this:

  our ($VERSION) = '$Revision: 1709 $' =~ m{ \$Revision: \s+ (\S+) }x;

NOTES

Conway recommends using the version pragma instead of raw numbers or 'v-strings.' However, this Policy only insists that the $VERSION be defined somehow. I may try to extend this in the future.

AUTHOR

Jeffrey Ryan Thalhammer <thaljef@cpan.org>

COPYRIGHT

Copyright (c) 2005-2007 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.