Re: Module name suggestion

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]

Comment on Re: Module name suggestion Download Code

Replies are listed 'Best First'.
Re^2: Module name suggestion by Anonymous Monk on Dec 23, 2010 at 15:00 UTC
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]

Replies are listed 'Best First'.

Re^2: Module name suggestion
by Anonymous Monk on Dec 23, 2010 at 15:00 UTC

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]