Hi --

Each module or program I'm writing as part of a larger system starts with the same litany of 'use' code. I feel like I am typing the same structural code over and over, then woe to me should I need to make a change (as when I recently decided to use the warnings pragma throughout). 

use strict; 
use warnings;

package Foo::Bar;

use Data::Dumper;
use Log::Log4perl;
my $log = Log::Log4perl->get_logger(__PACKAGE__);
use MyDBI;
use MyLWP;
etc etc etc

[download]
Would it be considered Bad Form to toss all of these into a Common.pm file and then require them? My thought is to start each module with 
package Foo::Bar;
require Common;

[download]
Any pitfalls of this? Would I want a "use" or a "require" here? Would each package get their own copy of $log with the correct package name?

Thanks for your advice.

rkg

In reply to standard require by rkg

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.