I've separated subroutines into several files that I load into the main script using require
That sounds like Perl 4-style, around 20 years behind the curve. Place your subroutines into one or more modules. Make each module testable in isolation. To put that to the proof, write some unit tests for each module. See perlmod and Test::More.

I have some global variables that I define in the main script, and that are used throughout the sub-scripts
Global variables are evil. Ruthlessly eliminate them. Clearly define the inputs and outputs of each of your subroutines. With that done, eliminating the nasty globals should be a doddle.

I heard, for the first time, that it's good practice to "use strict"
In addition to "use strict", add "use warnings".

In reply to Re: Using variables in require file... not possible? by eyepopslikeamosquito
in thread Using variables in require file... not possible? by tunafish

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.