Bio::Root Version
SummaryPackage variablesSynopsisDescriptionGeneral documentationMethods
Bio::Root::Version - provide global, distribution-level versioning
Package variables
No package variables defined.
  package Bio::Tools::NiftyFeature;
require Bio::Root::RootI;
# later, in client code: package main; use Bio::Tools::NiftyFeature 3.14; ## alternative usage: NiftyFeature defines own $VERSION: package Bio::Tools::NiftyFeature; my $VERSION = 9.8; # later in client code: package main; # ensure we're using an up-to-date BioPerl distribution use Bio::Perl 3.14; # NiftyFeature has its own versioning scheme: use Bio::Tools::NiftyFeature 9.8;
This module provides a mechanism by which all other BioPerl modules
can share the same $VERSION, without manually synchronizing each file.
Bio::Root::RootI itself uses this module, so any module that directly
(or indirectly) uses Bio::Root::RootI will get a global $VERSION
variable set if it's not already.
No description
Methods description
None available.
Methods code
sub import {
    # try to handle multiple levels of inheritance:
my $i = 0; my $pkg = caller($i); no strict 'refs'; while ($pkg) { if ($pkg =~ m/^Bio::/o &&
not defined ${$pkg . "::VERSION"}) {
${$pkg . "::VERSION"} = $VERSION;
} $pkg = caller(++$i); } } 1; __END__
General documentation
Mailing ListsTop
User feedback is an integral part of the evolution of this and other
Bioperl modules. Send your comments and suggestions preferably to one
of the Bioperl mailing lists. Your participation is much appreciated.                  - General discussion - About the mailing lists
Support Top
Please direct usage questions or support issues to the mailing list:
rather than to the module maintainer directly. Many experienced and
reponsive experts will be able look at the problem and quickly
address it. Please include a thorough description of the problem
with code and data examples if at all possible.
Reporting BugsTop
Report bugs to the Bioperl bug tracking system to help us keep track
the bugs and their resolution. Bug reports can be submitted via the
AUTHOR - Aaron MackeyTop
The rest of the documentation details each of the object
methods. Internal methods are usually preceded with a _