I have a file like this saved as /var/ldt/ldt.conf :
LDT_HWADDR='00:00:00:00:00:00'
LDT_DISK='/dev/sda'
LDT_OS_ID='24'
LDT_VERBOSE=true
RUN_UPDATES=true
I want to source it in a way that in my perl code I could use the exact key names and will be able to do something like this:
print $LDT_HWADDR;
print $LDT_OS_ID;
print $RUN_UPDATES;
Desired output would be:
00:00:00:00:00:00
24
true
Just use a hash:
#!/usr/bin/perl -w
use strict;
open(my $fh, "<", "/var/ldt/ldt.conf") || die "Can't open file: $!\n";
my %vars;
while(<$fh>){
## remove trailing newlines
chomp;
## Split the line on =
my @F=split(/=/,$_,2);
## remove quotes
$F[1]=~s/^['"]//;
$F[1]=~s/['"]$//;
## Save the values in the hash
$vars{$F[0]}=$F[1];
}
print "LDT_HWADDR:$vars{LDT_HWADDR}\n";
print "LDT_OS_ID:$vars{LDT_OS_ID}\n";
print "RUN_UPDATES:$vars{RUN_UPDATES}\n";
Output:
LDT_HWADDR:00:00:00:00:00:00
LDT_OS_ID:24
RUN_UPDATES:true
Alternatively, use $$var. Note, however, that such things are very rarely, if ever, a good idea and very often lead to complications (for example, see the link provided by @Sobrique in the comments). The approach above is much safer.
#!/usr/bin/perl
open(my $fh, "<", "/var/ldt/ldt.conf") || die "Can't open file: $!\n";
while(<$fh>){
## remove trailing newlines
chomp;
## Split the line on =
my @F=split(/=/,$_,2);
## remove quotes
$F[1]=~s/^['"]//;
$F[1]=~s/['"]$//;
## Set the variables
${$F[0]}=$F[1];
}
print "$LDT_HWADDR\n";
print "$LDT_OS_ID\n";
print "$RUN_UPDATES\n";
$$var. That's a really excellent way to create some really awful bugs. perl.plover.com/varvarname.html
perlvar. You'll make your code do all manner of extremely fruity things, and the source of the glitch will be the config file.
print "$LDT_HWADDR\n"). If the OP can accept $h->{LDT_HWADDR} or $h{LDT_HWADDR} it would lead to much much cleaner (and probably safer) code.
@F with split - I rather like the idom my ( $key, $value ) = split ( /=/ );