It is usually easier to treat errors and special cases with Perl rather than a regex. In this case, do one field at a time. I do not know the error processing that you need, but this should get you started.
use strict;
use warnings;
use Test::More tests=>2;
my $raw_path = '$HOME/work_dir/${TOOL_NAME}/$VERSION';
my $required_path = 'home/work_dir/hammer/1.01';
my %env = ( # Dummy hash for testing
HOME => 'home',
TOOL_NAME => 'hammer',
#VERSION => '1.01', # Removed to force error
);
sub resolve_env_in_path {
my ($path) = @_;
while ($path =~ m/\$\{?(\w+)\}?/) {
my $field;
if( exists($env{$1}) ) {
$field = $env{$1};
}
else {
warn "Invallid path";
$field = 'UNSPECIFIED';
}
$path =~ s/\$\{?(\w+)\}?/$field/;
}
return $path;
};
ok( resolve_env_in_path($raw_path) ne $required_path, 'error expected'
+ );
$env{VERSION} = '1.01';
ok( resolve_env_in_path($raw_path) eq $required_path, 'good' );
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.