comment on

I am sorry, but I can't make sense of your answer. :-( If the part marked as "code" is supposed to be a script that works - well, it doesn't; it just produces a bunch of errors.

But let's concentrate just on the regular expression, because this is what I asked for. Sadly, that doesn't work, either. :-(

Let's start with something easy:

my $data = "\@include test";
if ($data =~ /\@include\s+('[^']+'|"[^"]+"|.+?(?<!\\))\s+/g)
{
    print "File name: \"$1\"\n";
}
[download]

This doesn't output anything at all, meaning that the parsing fails.

If we set

my $data = "\@include \'test test\'";

this outputs

File name: "'test"

which is totally wrong. It should output

File name: "test test"

If we try

my $data = "\@include \"test test\"";

this produces the similarly wrong

File name: ""test"

And finally, if we try

my $data = "\@include test\\ test";

it also produces no output, meaning that the matching fails

Any better suggestions?

In reply to Re^2: Help with a regular expression for file name parsing by bontchev
in thread Help with a regular expression for file name parsing by bontchev

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.


Pathologically Eclectic Rubbish Lister
	PerlMonks