Regexp::Assemble would not track the original pattern correctly. I give up, it's too hard for me :(

use Regexp::Assemble;
my $patterns = "/path/to/file.txt";
my $list_regex = Regexp::Assemble->new(file => $patterns);
$list_regex->track( 1 );

open( FILE, "<", "$arg1") or die "$arg1: $!\n";
while (<FILE>) {
    if (/$list_regex/) {print "\n$arg1\n$list_regex->matched\n";}
    }
close(FILE);
}
[download]

Now I have this code but I'm facing a new problem. In my first example I use both flags /is I need /s so . to match newlines as well. I have this

my $patterns = "/path/to/file.txt";
my $arg1 = shift;

open( PATTERNS, "<", $patterns ) or die "$patterns: $!\n";
my @list_patterns = <PATTERNS>;
close PATTERNS;
chomp @list_patterns;

my $regexStr = "(" . join("|", @list_patterns) . ")";
    my $list_regex = qr{$regexStr}i;
    
    open( FILE, "<", "$arg1") or die "$arg1: $!\n";
    while (<FILE>) {
        if (/$list_regex/) {print "\n$arg1\n$1\n";}
        }
    close(FILE);
[download]


Adding s to both
my $list_regex = qr{$regexStr}is; or
if (/$list_regex/is)
would not solve the problem.


part1.*part2
[download]

This pattern working with my original script. .* should match also newline.

fggffgfg
part1
hghggh
ghhggh
hggh


part2
ytyty
[download]

This is the last problem, else the script working perfectly and much faster thanks to your advices. I will next take a look at local $/.

You say that you "need /s so . to match newlines as well", and I assume this means that if your pattern list includes something like foo.*?bar, you would want that to match either of the following examples (where I'll put parens around the intended match):

example 1: blah (foobar) blah

example 2: blah (foo
all sorts of content on
lots of lines
of data 
bar) blah
[download]

In that case, you need to read the data file in slurp mode:

my $regex_string = join '|', @list_patterns;

open( FILE, "<", $arg1 ) or die "$arg1: $!";
$_ = do { local $/; <FILE> };  # temporarily set $/ = undef to slurp f
+ile
close FILE;

if ( /($regex_string)/is ) {
    # got a match...
}
[download]

Regarding the placement of parens and regex qualifiers, you could do that in other ways, like:

my $list_regex = qr/($regex_string)/is;
...
if ( /$list_regex/ ) {
...
[download]

No difference, really, but when there's a choice, I like having the parens visible in the code near the place where I use $1, $2, etc.

...but I don't know what's really indented...

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
    <loc>http://test.com/index.html</loc>
    <lastmod>2009-08-21</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.7</priority>
    </url>
<url>
    <loc>http://test.com/page_1.html</loc>
    <lastmod>2009-08-06</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
    </url>
<url>
    <loc>http://test.com/page_2.html</loc>
    <lastmod>2009-08-10</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.4</priority>
    </url>
[download]

<a href=.*<a href=.*poker
page.{0,10}.html.*page.{0,10}.html.*page.{0,10}.html.*map
[download]

<a href=.*<a href
page.{0,10}.html.*page.{0,10}.html.*page.{0,10}.html
[download]

You say that you want to capture and print the string that matches, but you aren't getting the output you expect? Your examples don't make any sense to me. (How does that xml snippet relate to anything?)

If you're still having a problem with capturing and printing matches the way you want, you should post a minimal, self-contained example consisting of:

• runnable code
• a file containing some regex patterns
• a data sample containing the kind of pattern you want to capture.
Maybe in the process of putting that together, you'll realize where the problem really is, and solve it on your own. Good luck.

Ok, to be more clear.

I have this code:

#!/usr/bin/perl -w

use strict;

my $patterns = "/path/to/patterns.txt";
my $arg1 = shift;

open (PAT, '<', $patterns) or die "$patterns: $!\n";
my @patterns = <PAT>;.
close(PAT);
chomp @patterns;

my $regex_string = join '|', @patterns;

open( FILE, "<", "$arg1") or die "$arg1: $!\n";
$_ = do { local $/; <FILE> };
close(FILE);

if ( /($regex_string)/is ) {print "\n$arg1\n$1\n";}
[download]

Test list with patterns:
/path/to/patterns.txt

part1.*part2
Foo bar
Other pattern
[download]

Test file to scan:

hghghgghghh
part1
fff
part2

jhhjhjkjk

Foo bar
kkjkjkj
Other pattern
[download]

$1 will show all wildcarded text between part1 and part2 and not only the pattern part1.*part2 as it should.

/path/to/file
part1
fff
part2
[download]


Also, only first pattern found is displayed now. That's not a problem, but I'd also like to know how to display all patterns if a file contains more than one.
Please bear an unexperienced user like me. Thank you!
Regarding the other problem with xml file to scan, I must do more tests to know exactly where the problem is.

Thank you very much for your reply. I can't check the code these days, but I will let you know how it's going asap.

Graff, you're an awesome guy!! The final version of the script working exactly in the manner I want except a little problem.
I will elaborate it.

I have this file to scan: example.txt (used by scammers/abusers)
http://uploading.com/files/get/cm3364a5/
This pattern

page.{0,10}html.*?page.{0,10}html.*?</changefreq
[download]

working because example.txt contain all elements of pattern.

If I change pattern to

page.{0,10}html.*?page.{0,10}html.*?kkk
[download]

(example.txt doesn't containt kkk), script enters a loop and CPU usage become very high.
I think it's related to excesive number of the same pattern, because reducing example.txt to only few lines solves the problem.
Any idea how to solve this bug?