Re: Identifying the current opened filehandle for writing as I'm getting undefined variable concatenation errors

2014-01-14 Thread Matt McAdory
The comma was a pseudo code error. Should have read = print $FH "some stuff\n"; # works great. = I will test for undef on $thing. Thanks for looking. Pretty sure I printed the expected result to STDOUT without error. The module call involves a telnet across the network, maybe the open I added prov

Re: Identifying the current opened filehandle for writing as I'm getting undefined variable concatenation errors

2014-01-14 Thread Rob Dixon
On 15/01/2014 03:09, Matt McAdory wrote: Is there a method for determining the currently selected filehandle? should I always check for undef and open my filehandle before writing to it? use strict; use warnings; use autodie qw (:all); use My:CustomMod_with_FH_write; open (my $FH, ">", "filena

Re: Identifying the current opened filehandle for writing as I'm getting undefined variable concatenation errors

2014-01-14 Thread Brian Fraser
On Wed, Jan 15, 2014 at 12:09 AM, Matt McAdory wrote: > Is there a method for determining the currently selected filehandle? > should I always check for undef and open my filehandle before writing to it? > > use strict; > use warnings; > use autodie qw (:all); > > use My:CustomMod_with_FH_write;

Identifying the current opened filehandle for writing as I'm getting undefined variable concatenation errors

2014-01-14 Thread Matt McAdory
Is there a method for determining the currently selected filehandle? should I always check for undef and open my filehandle before writing to it? use strict; use warnings; use autodie qw (:all); use My:CustomMod_with_FH_write; open (my $FH, ">", "filename.txt"); my $var = My:CustomMod_with_FH_w

Re: Package version numbers

2014-01-14 Thread John SJ Anderson
> Thanks for the test, John. In the book's example, they have: > > use v5.10; > > so I thought I was new enough, but maybe not. http://use.perl.org/use.perl.org/articles/10/04/13/1953252.shtml also notes it as a new feature in 5.12. I'm sure the authors regret the typo. ;^) j. -- To

Re: Package version numbers

2014-01-14 Thread SSC_perl
On Jan 14, 2014, at 4:04 PM, John SJ Anderson wrote: > I'm not sure exactly when that syntax was added, but for what it's > worth, it fails with 5.10.1 here too. Perl 5.12.5, on the other hand, > works. > > You may just need to upgrade. Thanks for the test, John. In the book's example, t

Re: Package version numbers

2014-01-14 Thread John SJ Anderson
On Tue, Jan 14, 2014 at 2:50 PM, SSC_perl wrote: > I'm trying to number packages the way it's written about on page 406 > of Programming Perl, 4th ed., e.g. > > package Emailer 1.01; > > However, when I do that, I get the following error: > > syntax error at ss_files/Emailer.pm line 1, ne

Package version numbers

2014-01-14 Thread SSC_perl
I'm trying to number packages the way it's written about on page 406 of Programming Perl, 4th ed., e.g. package Emailer 1.01; However, when I do that, I get the following error: syntax error at ss_files/Emailer.pm line 1, near "package Emailer 1.01" Compilation failed in require at adm

Re: Still Trying to Understand Perl Module Control Process

2014-01-14 Thread David Precious
On Mon, 13 Jan 2014 10:32:14 -0600 "Martin G. McCormick" wrote: > I am using cpanp or cpan plus to handle perl modules on > a FreeBSD system. If I give the command > > cpanp -i Net::DNS > it installs Net::DNS 0.73. Normally, this is exactly what one > would want it to do but Net::DNS0.73 i

Still Trying to Understand Perl Module Control Process

2014-01-14 Thread Martin G. McCormick
I am using cpanp or cpan plus to handle perl modules on a FreeBSD system. If I give the command cpanp -i Net::DNS it installs Net::DNS 0.73. Normally, this is exactly what one would want it to do but Net::DNS0.73 is buggy. At least one bug causes domain name server or DNS updates to fail s