I haven't seen any PErl code with -log- like that before. I've only seen code
like that with = error(*).
-Original Message-
From: Patton, Billy billy.pat...@h3net.com
Sent: Oct 6, 2014 9:33 AM
To: beginners-cgi@perl.org beginners-cgi@perl.org
Subject: cgi and inheritance
I’ve recently
Hello!
Let's consider following strip-down example:
# file a.pl
use strict;
package a;
our $var=1;
warn var=$var;
# file b.pl
use strict;
#no strict qw/vars/;
require 'b.pl';
package a;
warn var=$var;
How to get rid of no strict qw/vars/; to not get message Global symbol
$var requires explicit
On 9 October 2014 03:35, Hans Ginzel h...@matfyz.cz wrote:
Hello!
Let's consider following strip-down example:
# file a.pl
use strict;
package a;
our $var=1;
warn var=$var;
# file b.pl
use strict;
#no strict qw/vars/;
require 'b.pl';
package a;
warn var=$var;
How to get rid of
The ‘our’ statement associates a simple name with a package global variable in
the current package. Therefore, if you want to make $var in file b.pl mean the
package global variable $var in package a ($a:var), just put ‘our $var;’ after
the ‘package a;’ statement in file b.pl (see below).
On
Hi!
When creating the base for a new CPAN module using h2xs (e.g. with the
command h2xs -b 5.10 -XA -n Super::Duper::Module), there is a lib folder
created.
In this lib folder, the name space is mirrored by a directory tree (e.g.
lib/Super/Duper/Module.ppm).
Now, while browsing CPAN, I noticed
On 9 October 2014 08:36, Hans Ginzel h...@matfyz.cz wrote:
I want to use one global hash variable for options or configuration
variables
like verbose, debug. I don't want to pass them to each function
or to almost each object.
Indeed, Jim Gibson explains you can simply declare our in both
