perl-module

I'm a bit confused by conflicting advice between pre-5.10.0 documents and the more recent version module. Perl Best Practices makes it pretty clear that version strings ('v1.0.3') are bad and one is supposed to specify a version as follows: use version; our $VERSION = qv('1.0.3'); but the version module says that we're back to using version strings: use version 0.77; our $VERSION = qv("v1.2.3"); Have we regressed, or is there a reason behind this? ire_and_curses Your quote from Perl Best Practices is not quite right. Specifically, bare vstrings of the form our $VERSION = v1.0.3; are

I can print out Host UP Time percentage from Nagios-Report Perl Module with following code: #!/usr/bin/perl use strict ; use Nagios::Report ; my $x = Nagios::Report->new(q<local_cgi localhost nagiosadmin>) or die "Can't construct Nagios::Report object." ; $x->mkreport( [ qw(HOST_NAME PERCENT_TOTAL_TIME_UP) ], sub { my %F = @_; my $u = $F{PERCENT_TOTAL_TIME_UP}; $u =~ s/%//; }, 0, sub { my $F = shift @_ ; } ) ; $x->debug_dump ; But How can I only print out Service UP Time Percentage? I mean only output the percentage value. I tried many options but couldn't get it right. This will produce

Looking to execute a perl script on a remote machine via a Perl script. Appears one option is to use system() function and create an ssh key so the password is not required. Which leads me to the focus of this question, the other option appears to be to install and run one of these perl modules: Net::SSH Net::SSH2 Net::OpenSSH Besides the protocol used, what else should I be comparing with these Perl modules? indiv The Net::OpenSSH documentation has a section describing the pros and cons of each. Here are some excerpts related to the ones you are asking about, but the documentation lists more:

I have the same question as was asked HERE but unfortunately I cannot install Moose and I think the solution described there was particular to Moose. Can someone tell me how to the same in old school "use base" speak? To reiterate the question, I would like to have my base classes to have an automatic logging mechanism using Log4perl so if the user does not do anything I get some reasonable logging but if the user of my class needs/wants to overwrite the logger they can. Well, if you want to have role/mixin type behavior and such just like in the other answer, you could use vanilla multiple

This is an interesting Perl behaviour. (atleast to me :) ) I have two packages PACKAGE1 and PACKAGE2 which exports function with same name Method1() . As there will be so many packages which will export this same function, use -ing everything in a Perl file will be tedious. So, I have created a general include file INCLUDES.pm which will have these use s. INCLUDES.pm: use PACKAGE1; use PACKAGE2; 1; PACKAGE1.pm: package PACKAGE1; use Exporter; our @ISA = qw(Exporter); our @EXPORT = qw ( Method1 ); sub Method1{ print "PACKAGE1_Method1 \n"; } 1; PACKAGE2.pm: package PACKAGE2; use Exporter; our

Question : What is considered to be "Best practice" - and why - of handling errors in a constructor?. "Best Practice" can be a quote from Schwartz, or 50% of CPAN modules use it, etc...; but I'm happy with well reasoned opinion from anyone even if it explains why the common best practice is not really the best approach. As far as my own view of the topic (informed by software development in Perl for many years), I have seen three main approaches to error handling in a perl module (listed from best to worst in my opinion): Construct an object, set an invalid flag (usually " is_valid " method).