strict is your friend - it'll save you a lot of debugging (mistyped variable names, etc.).

As for using or requiring a file to set variables, you could do that, but you probably don't want to.

What might make sense is to write a function in a second perl script that reads a file containing your parameters and returns them as, say, a hash-reference.

e.g. (not fully tested)

require 'test_03.pl'; my $result = SetVars(); foreach(keys %{$result}){ print "$_ : ${$result}{$_}\n"; }

and then in test_03.pl:

use strict; sub SetVars(){ my %vars; open(VARS, 'myvars.txt')||die "Cannot open myvars.txt:$!\n"; while(<VARS>){ chomp; $vars{(split /:/)[0]} = (split /:/)[1]; } return \%vars; } return 1;
Tom Melly, tom@tomandlu.co.uk

In reply to Re: Perl configuration files by Melly
in thread Perl configuration files by rbnorthcutt

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.