Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

In my project (say Foo), instead of writing:

use 5.010;
use autodie;
use strict;
use warnings;

[download]

and perhaps a few more lines in the future, I want to consolidate this into a single use statement, much like 'use Modern::Perl'. So all my project modules (and scripts) will begin with this preamble.

What would be a good name for this module? Foo? Modern::Foo?

Replies are listed 'Best First'.
Re: Module name suggestion
by Corion (Patriarch) on Dec 23, 2010 at 12:41 UTC

    Maybe Foo::Common or Foo::Preamble?

[reply]
[d/l]
[select]
Re: Module name suggestion
by JavaFan (Canon) on Dec 23, 2010 at 14:18 UTC 
    I::am::too::lazy::to::come::up::with::an::editor::macro;
I::like::to::have::people::wonder::why::I::did::not::enable::warnings:
+:or::strict;
I::wonder::what::is::in::this::module;
This::enables::features::without::saying::so;
Everyone::knows::what::strict::and::warnings::do::noone::knows::my::mo
+dule;
I::leave::people::guessing::what::is::in::this::common::module;
Modern::the::three::year::old::version::of::perl;
This::common::Foo::module::does::not::provide::anything::Foo::specific
+::Neither::does::it::provide::any::logic;

    [download]
[reply]
[d/l]

      Even if you don't have to type it (using macro/template), you still have to look at it. Visual clutter or overload, I say.

      This is for an (internal) project, so chances are greater that every developer knows it.

      It follows DRY principle. If I can group several statements into a sub, why can't I also group several directives/preamble into one line?

      The Foo::common does provide something Foo-related: setting policy for every Foo module.

[reply]
Re: Module name suggestion
by JavaFan (Canon) on Dec 23, 2010 at 14:21 UTC
    I suggest using a name that tells what it does. Which would mean something like: 
    use StrictWarningsAutodieAnd510Features;

    [download]
[reply]
[d/l]
      I get the sarcasm, but aside as a shorthand, Foo::common also serves another important function: enforcing uniform policy. It's easier in the future to deprecate something, etc.
[reply]

        Foo::Policy ?

[reply]
Re: Module name suggestion
by moritz (Cardinal) on Dec 23, 2010 at 18:32 UTC
[reply]
Re: Module name suggestion
by Anonymous Monk on Dec 23, 2010 at 14:00 UTC
[reply]
      But it neither provides anything related to Foo, nor does it have any tools. It's about an as bad misnomer as Blue::Wednesday would be.
[reply]
[d/l]
        It seems directly related to Foo, because Foo is going to be the sole or primary consumer. And while you may think that using ToolSet with pragmas instead of more meaty modules isn't using it with "tools", you'd be wrong.
[reply]
Re: Module name suggestion
by Anonymous Monk on Dec 23, 2010 at 19:22 UTC
[reply]

Back to Seekers of Perl Wisdom