As msh said somewhat tersely check out File::Path and read the doco.

Here is a sample of its use:

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

use strict;
use diagnostics;
use warnings;
use File::Path;

mkpath(["/usr/tmp/over/the/rainbow"],1,0755);
[download]

Peter @ Berghold . Net

Sieze the cow! Bite the day!

Test the code? We don't need to test no stinkin' code! All code posted here is as is where is unless otherwise stated.

Brewer of Belgian style Ales

Awesome. That's what I needed.

Thanks, esh and blue_cowdawg.

-- ccarden

 Others have already answered - but if you want a literal equivilent you could do worse than look at the Perl Power Tools project.

 This aims to rewrite lots of standard utilities in pure perl.

• here is the 'mkdir' entry.

    system mkdir => '-p' => @dirs;
[download]

After all, that's why we have a Unix toolkit - it's not a shame to use it.

And yeah, I know that doesn't work on Windows. But I said that I tend to use it, and I don't do Windows. ;-). (But if I do, I install cygwin, and I've a Unix toolkit).

Abigail

Ahh, but here is the real problem: certain customers forbid us from changing the platform load. Has anyone else run into this? It's very common with many of the projects that I have worked on in the Detroit area.

Security and system administration are very, very tight at the auto companies. Everything must be served, and if I want to use cygwin, I'd have to jump through hoops to serve it along with the desired version of perl. Btw, perl is frowned upon quite seriously at the autos. The patent response from certain admins is: "Who's going to support it? If it breaks, who do I call, the Internet? Ha. Ha. Ha."

Geez, Louise.

So, for now, the answer is that we keep one server at the back end of our system that runs all of our perl scripts. This allows us to use perl without running into too many complaints. But the server could easily change from *nix to win32 in a year. So my code needs to be able to run if such a change occurs.

Thanks to everyone for the valuable input.

-- ccarden

And did you tell them you can buy commercial support for Perl?

Also, ask them in which language they like there server-side programs to be run in? Python and PHP suffer the same "problems" as Perl. If it's written in C, changing from Unix to Windows won't be trivial. Which leaves Java?

Abigail

`mkdir -p a/b/c`;
[download]

That's how the code currently reads, but I need it to be portable.