Do you really need the config file to define lexical variables --- or would populating a config hash suffice? If so there are various config modules on CPAN. A very simple and direct method is to define an anonymous hash in the config file and capture it via require --- as in this node. As erikharrison mentions, any code evaluation solution (as opposed to a parsing solution) means you trust the code in the config file.

You can't read lexical variables from an external file and see them in your file. With strict or without. That's one of the scope restrictions dictated by my.

Anyway, you can't escape when use strict is in effect, but you shouldn't do without. Consider two alternative solutions:

1: Create a module and export the variables you need from there. See perldoc perlmod and perldoc Exporter

2: Use OOP. A quick-and-dirty solution could be to create a bare bones class with some attributes you can pull out via class or object methods, but it's not that elegant :-). I'll write some untested crap below here, but you should really look for something better that fits your needs

package MyProgramConfiguration ;

use strict ;
use warnings ;

# Take this as a starting point,
# *NOT* as an example, *PLEASE*!!!
my %config = (
  color => 'yellow',
  beverage => 'chinotto',
  food => 'pizza',
  driver => 'Schumacher',
) ;

my gimmeconf {
  # I don't care how you called me (class or object method)
  return %config ;
}
[download]

And your prog could do:

use strict ; # don't leave it out
use MyProgramConfiguration ;

my %c = MyProgramConfiguration->gimmeconf() ;
[download]

In case I didn't say that, I'll say it again: don't take this as production code!!! Read it, understand how it works and create your solution from scratch. You have been warned. Also, you should read about lexical variables and how they work.

Ciao!
--bronto

# Another Perl edition of a song:
# The End, by The Beatles
END {
  $you->take($love) eq $you->made($love) ;
}

A solution might be to use our in the config file. Or, possibly, no strict. But be sure that the code in the file is safe (for some definition of safe, based on the environment the code will be used in).

Light a man a fire, he's warm for a day. Catch a man on fire, and he's warm for the rest of his life. - Terry Pratchet

use Config::Properties. It is the easiest way that I know.

Code first

use Config::Properties;
use Data::Dumper;
my $propertyFile = new Config::Properties;

  open (FD, "property.properties") or die "Could not open file: !$";
  $propertyFile->load( (*FD) );
  close(FD);

  print Dumper $propertyFile;
[download]

Now a external properties file. save as property.properties

var = value
one = 1
two = 2
oneandone = 2
[download]

HTH - Kristofer

#!/usr/bin/perl
use strict;
our ($a,$b);
require config;
print "$a\t$b\n";
[download]

Oops, I forgot, the config file must have a 1; as the last line; to satisfy the Perl gods.