Would it be considered Bad Form to toss all of these into a Common.pm file and then require them?
IMHO, no (not that it makes much difference since you can only ever require a module once (without munging %INC, of course)). However this won't work for lexically scoped pragma such as strict and warnings, as they will only apply their particular pragmatic effects to the given lexical scope. So you will have to explicitly include the likes of strict into your desired modules. You'd also want to make sure that the the importing from the modules in Common is bubbled up to the caller's module e.g so the Dumper function from Data::Dumper can be called without fully qualifying it (i.e it's been imported into the caller's package).
Would each package get their own copy of $log with the correct package name?
Again, because of lexical effects $log will not be visible in external modules. In this particular case you could either use a function such as Common::log to return a lexically scoped $log or just have a $log package variable e.g $Common::log. Search around for singleton objects for more information on the subject.
HTH

_________
broquaint


In reply to Re: standard require by broquaint
in thread 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.