Shawn Corey misstated the issue, it isn't that -w can't be turned off, the
problem is that it is turned on globally rather than lexically. That is, it
forces warnings onto modules that may have been designed to not use
warnings:
$ cat T.pm
package T;
sub foo {
my $x = shift;
# und
On Sun, 2017-07-02 at 11:16 -0400, Shawn H Corey wrote:
> On Sun, 2 Jul 2017 14:29:25 +0200
> Eric de Hont wrote:
>
> > What it boils down to: use warnings as well as -w works, but -w is
> > considered old fashioned.
>
> The problem with -w is that it can't be turned off.
$ perl -le'
use warni
Op 02-07-17 om 17:16 schreef Shawn H Corey:
On Sun, 2 Jul 2017 14:29:25 +0200
Eric de Hont wrote:
What it boils down to: use warnings as well as -w works, but -w is
considered old fashioned.
The problem with -w is that it can't be turned off. Sometimes a module
has to do something dangerous
On Sun, 2 Jul 2017 14:29:25 +0200
Eric de Hont wrote:
> What it boils down to: use warnings as well as -w works, but -w is
> considered old fashioned.
The problem with -w is that it can't be turned off. Sometimes a module
has to do something dangerous and having a warning appear is annoying
at
On 07/02/2017 03:29 PM, Eric de Hont wrote:
[snip]
> Apart from the perldocs also have a look at https://perlmaven.com/hashbang
[snip]
Thanks. That was a good link.
perlintro(1) was good to review but the perlmaven link went into some
nice depth. They say opposite things about using '#!/usr/bi
Op 02-07-17 om 10:52 schreef Lars Noodén:
I've grepped the first lines of a large project's source files for
instances of the string perl as a word. Sorted, ranked, and slightly
edited, the results can be seen below. What I am wondering is that can
anything general, independent of context be sa
