Update: Oops! I originally suggested File::Path instead of File::Spec.

I think this will be a very good thing for all future development.

I am looking for examples so I can see how it works.

Thanks

Prost,
Moe

my $path = "$DRIVE_LETTER/tmp/$some_file";
[download]

myocom is correct about the relative paths, but I'd go just a bit further and remind you that perl understands the root of the drive that it is being executed from. In other words, if you're installed in D:\Perl\bin\perl.exe, then / = D:\

This is true for all Windows as far as I know...

#!/home/bbq/bin/perl
# Trust no1!

The Environment vars will be set up correctly. And I forgot the "" around the path in the example... but that will be correct also. I looked at File::Path and it appears to be used for making and deleting directory trees. Not really what I'm looking for... I need a porting kind of solution for existing code.

There are 4 distinct drives(c:,j:,k:,l:) I have to access from the Win2000 systems. On unix they are simply paths. The unix systems are running in production as we speak.

My concern is that there are well over 50,000 lines of code now and I need a good and simple as possible solution to the drive mapping issue.

My idea is just that... an idea. I know there must be a better way because I'm relatively new to programming and how is it possibly for me to come up with the best idea as my first attempt?

So... looking back at my syntactically incorrect "idea"... can anyone tell me if the concept is correct or if there is a better way?

Prost,
Moe

Your idea will probably work fine. Assuming that the environment variable 'SOME_DRIVE' contains something like 'J:', you might also consider something like this:

$path = '/tmp/some/path';
$path = $ENV{SOME_DRIVE} . $path if $^O eq 'MSWin32';

# rest of code
[download]

I thought of that also. Is that more stable? If so I will use it.

Prost,
Moe

Doh, sorry. I meant File::Spec, not File::Path. File::Spec is good for handling paths in a platform independent manner.