Perl::Critic::Policy::Modules::RequirePerlVersion - Expect a
use 5.006; or similar
As Perl evolves, new desirable features get added. The best ones seem to break backward compatibility, unfortunately. As a favor to downstream developers, it's good to state explicitly which Perl version will not be able to parse your code.
For example, the
our keyword was first appeared in a stable Perl in version 5.6.0. Therefore, if your code employs
our, then you should have a line like this near the very top of your file:
The former is preferred as the latter can trigger v-string compatibility warnings. (If someone could please explain that to me, I'd really appreciate it!)
Additionally, it's good form to state that minimum version in your Makefile.PL or Build.PL file.
Chris Dolan <email@example.com>
Copyright (c) 2006-2007 Chris Dolan
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.