Using do or eval to parse files like your work.conf is potentially very dangerous. Arbitrary Perl code can be inserted in files like that.

I have used Data::Undump with some success to more safely read data from files like your work.conf

However, since you are interested in only the values for $folder and license, you could extract those with regular expressions

(Untested)

use strict; use warnings; my $dir; my $lic; my $cfgf = 'work.conf'; open my $cfgh, '<', $cfgf or die "Can't open $cfgf: $!\n"; while (<$cfgh>) { if (/\$folder\s+=\s+'([^']+)'/) $dir = $1; next; } if (/license\s+=>\s+'([^']+)'/) { $lic = $dir . $1; last; } } print "Folder: $dir\nLicense: $lic\n";

In reply to Re: Recover a path from a config file by RonW
in thread Recover a path from a config file by Chaoui05

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.