Note that use strict boils down to

BEGIN { require 'strict.pm'; strict->import(); }
[download]

So strict->import() actually applies to the lexical scope one step outside of from where import() was called (or something like that). So, the following actually works:

package AID;

require strict;
require warnings;

sub import
{
    strict->import();
    goto &warnings::import;
}

1;
[download]

Then:

use AID;
BEGIN { print 0+""; }
print $x;
[download]

Gives:

Argument "" isn't numeric in addition (+) at - line 2.
Global symbol "$x" requires explicit package name at - line 3.
Execution of - aborted due to compilation errors.
[download]

And diagnostics.pm isn't lexically scoped (and I'm not sure why people even use it, to be quite frank), so you can just "use diagnostics" inside your common.pm file.

Brilliant! Makes perfect sense, but I wouldn't have even followed this thought process.

I'd recommend anyone implementing this should document it heavily!

#!/usr/bin/perl -w
[download]

But as far as I know, you'll have to use strict and diagnostics for each file.

Write a script to paste them in for you :)

Well, a more usual approach would to be to use whatever templating or skeleton facilities your editor provides (something like tempo mode or skeleton mode for Emacsen; I'm sure a vim using heathen will chime in with what they use :) to start off new programs from a base with everything you normally use.

Even if your editor doesn't provide such a facility natively you can always write your own template once and then copy that into a new file (perhaps even getting fancy and using Template Toolkit or the like to fill in variable parts).

Indeed. In fact I have used Komodo's template facility to do that in the past, except that it's pretty much as quick to type the two use lines so mostly I don't bother with the template.

OP's immediate problem seems to be different however - 50+ (presumed existing) files that need to be updated. Sounds like a Perl script to me rather than editor fu.

---

DWIM is Perl's answer to Gödel

You want the PERL5OPT environment variable. For example:

# MS-DOS:
set PERL5OPT=-Mstrict -Mwarnings
[download]

Not that I recommend this. If you do it at all, it should probably be in some launcher script, rather than at the system-global level.

Not a bug, but a very good case can be made for having strictures enabled by default. One has only to notice that about 30% of the "why doesn't this work" questions in SoPW would have been caught by OP if strictures had been included in OP's code to see that that is a good idea.

---

DWIM is Perl's answer to Gödel

There are a number of things I'd like to see done differently by default in Perl, including the strict pragma being on by default (though I'm not so sure about warnings) — and also default lexical scope so that I don't have to use my() all the time, and so that autovivification would create lexically scoped variables.

print substr("Just another Perl hacker", 0, -2);

- apotheon CopyWrite Chad Perrin