I prefer
Path::Tiny to handle paths for me:
#!/usr/bin/perl
use warnings;
use strict;
use feature qw{ say };
use Path::Tiny;
my $path = '/abc/def/ghi';
my $climb = path($path);
my @paths = $climb;
push @paths, $climb until ($climb = $climb->parent) eq '/';
say for @paths;
File::Spec is a core module that can handle the path as well:
#!/usr/bin/perl
use warnings;
use strict;
use feature qw{ say };
use File::Spec;
my $path = '/abc/def/ghi';
my @paths = 'File::Spec'->splitdir($path);
for my $i (reverse 0 .. $#paths) {
$paths[$i] = join '/', @paths[0 .. $i];
}
shift @paths; # Remove the empty path.
say for @paths;
But a regex with split will work similarly:
#!/usr/bin/perl
use warnings;
use strict;
use feature qw{ say };
use Path::Tiny;
my $path = '/abc/def/ghi';
my @paths = split m{(?<=.)/}, $path;
for my $i (reverse 0 .. $#paths) {
$paths[$i] = join '/', @paths[0 .. $i];
}
say for @paths;
I used a lookbehind assertion to skip the empty path before the first slash.
map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.