Handling uninitialized values

[THRAK]

I have a script that loops through a directory and it's sub-dir's. To get the files in the directory root I either make the sub-dir undefined or a null string. My question is a style and usage issue as "-w" complains if it's undefined. Is there a better way to do this sort of thing? Here's a quick test script of what I'm talking about:

#!/usr/local/bin/perl -w

use strict;

my $dir = '/tmp/';
my $sub_dir;
my $file = 'foo.txt';
my $path = "${dir}${sub_dir}${file}";

print "$path\n";

This causes the "Use of uninitialized value in concatenation" error. But if you set $sub_dir = ""; it halts the warnings. Just looked kind of odd/ugly, thus why you are reading this now.

-THRAK
www.polarlava.com

[Sifmole]

Or if $sub_dir is always going to be empty, then why are you using it?

I am assuming that you have some kind of loop going on where $sub_dir may or may-not be assigned. In that case I would try something like:

my $path = join('', $dir, ($foo || ''), $file);

This will fail if $foo == 0 so if that is a possibility then you could use..

my $path = join('', $dir, (defined $foo ? $foo : ''), $file);

[blue_cowdawg]

Very good point. If a var is going to be empty... toss it.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Peter L. Berghold --- [e-mail]
"Those who fail to learn from history are condemned to repeat it."

[THRAK]

If you read the question again, you will see the first thing I mentioned was that this was in a loop and the value is undefined when accessing files in the root location. This was only a small snippet to illustrate the point of the question.

-THRAK
www.polarlava.com

[blue_cowdawg]

Well... right off the bat without giving this much thought the first thing I can think of is

my $dir="/tmp";
my $sub_dir="/";

instead of putting the trailing slash in $dir put it in $sub_dir.

FWIW anyway...

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Peter L. Berghold --- [e-mail]
"Those who fail to learn from history are condemned to repeat it."

[rucker]

Well this isn't going to make it any prettier (in fact, it is uglier), but if you have potentially undefined variables and you want to suppress the warnings, you should check to see if they're defined and then use them or not. Here's one example... obviously there are other ways to do it.

my $path = defined($dir) ? $dir : '' . defined($sub_dir) ? $sub_dir : 
+'' . defined($file) ? $file : '';

[THRAK]

I've seen this sort of thing and would agree that is is uglier. I guess in a more complex application this might be good approach.

-THRAK
www.polarlava.com

[bwana147]

Yet Another Way Of Doing It

I would rather have the slashes not be part of the dirs or subdirs. Instead, consider that the full path merely consists of $dir, $sub_dir and $file, join'ed together with slashes. Then, grep should remove empty/undefined entries:

my $dir = '/tmp'
my $sub_dir;
my $file = 'foo.txt'

my $path = join('/', grep { defined && $_ ne '' } ($dir, $sub_dir, $fi
+le));
print "$path\n";

--bwana147

[bwana147]

You may disable warnings locally:

{
    no warnings qw( uninitialized );
    my $path = "${dir}${sub_dir}${file}";
}
print "$path\n";

Just my € 0.02
--bwana147

[THRAK]

I like this approach, but I guess a basic $sub_dir = '' is the quickest/cleanest solution here. Again, this is another example that would be very useful for a more complex piece of code.

-THRAK
www.polarlava.com