Hi there,

First, the situation:
I'm finally convinced (by Ovid's article) to change all my work to use 'strict' and 'perl -Tw'.
So I tried...

Next, the problem:
I've got a whole bunch of vars (like $rootpath, $rooturl, $sitename, $cgipath, etc. etc.) and some subroutines (like make_html, fatal_error, etc.) stuffed into two files, which are called by 'require "vars.pl" ' and 'require "sub.pl"'.
As you probably know, those vars aren't taken into the main-cgi-file, and there is my problem.
A thread like this has started earlier on, but all I found there terrified me: do I really have to change every line like
'print "path to cgi is $cgi_path";' into
'print "path to cgi is $whatever::$cgi_path";' ???
I'd have to do 50 hours of work if that's indeed the only possibility...

Last, the solution:
?

Might you know it, please let me know!!!

In reply to changing to strict-- problems with 'require files' by frinky

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.