in reply to Matching part of a path

Most of the time you should use File::Spec to manipulate paths. It has been bundled with Perl for forever, so there's no reason not to.
use File::Spec::Functions qw(canonpath splitdir); my (@path) = splitdir canonpath $path; # @path now contains ('', 'home', 'a', 'ff.pl') print $path[2], "\n";
But just as a point of interest, you have two alternatives: a regex-only solution would be simply
my ($userhome) = ($path =~ m!^/home/([^/]+)!);
This will match a string that starts with /home/, followed by at least one character that is not a slash, and will capture all these non-slash characters. The other way would be to split on slashes:
my @path = split m!/!, $path; # @path is now ('', 'home', 'a', 'ff.pl') print $path[2], "\n";

Note how I used $path instead of your $a. This is for two reasons - first of all, $a and $b carry a special meaning for the sort function in Perl, so you shouldn't use them elsewhere. And secondly, $a is not very descriptive. Variables and functions should always have descriptive names, lest you find yourself boggling at your own code after putting it aside for two weeks.

Also note how I used m!! instead of // to delimit the regular expressions. If you explicitly mention the m, Perl allows you to pick something other than forward slashes as delimiters, so you won't need to backwhack forward slashes inside the pattern. This is very handy to avoid "leaning toothpick syndrome". This and more is described in perldoc perlop.

Makeshifts last the longest.

Replies are listed 'Best First'.
Re: Re: Matching part of a path
by Hena (Friar) on Dec 16, 2003 at 07:56 UTC
    Note how I used $path instead of your $a. This is for two reasons - first of all, $a and $b carry a special meaning for the sort function in Perl, so you shouldn't use them elsewhere. And secondly, $a is not very descriptive. Variables and functions should always have descriptive names, lest you find yourself boggling at your own code after putting it aside for two weeks.

    Is this really true? You could use in sort $me and $my as well (any for that matter)? It should complain though if you are using scalars you've set up before (like doing double my).
      Quoting perldoc -f sort:
      If the subroutine's prototype is ($$), the elements to be compared are passed by reference in @_, as for a normal subroutine. This is slower than unprototyped subroutines, where the elements to be compared are passed into the subroutine as the package global variables $a and $b (see example below). Note that in the latter case, it is usually counter-productive to declare $a and $b as lexicals.
      Perl only complains when you try to doubly declare a lexical variable name in the same scope. The following won't produce a complaint:
      use strict; use warnings; my $foo; { my $foo; }

      Makeshifts last the longest.