You said:

Unfortunately, due to the large amount of data I have, I cannot understand if it's working...

How many lines in "query04.txt"? How many lines in "multisearch_final_sorted_3.txt"? If you create a test version of each file, containing just a few lines that should produce some output, does the script work correctly on those test files? (Hint: Allowing file names to be provided as command line args can help with testing.)

One way to try speeding things up is to create a single regex from your query file, by joining the lines with "|": 

#!/usr/bin/perl

use strict;
use warnings;

my $PATHDATA = ".";  # (you didn't say how this was being set)

my ( $query_list_file, $file_to_search ) = ( @ARGV == 2 ) ?
    @ARGV :
    ( "$PATHDATA/query04.txt", "$PATHDATA/multisearch_final_sorted_3.t
+xt" );

open( HH, "<", "$PATHDATA/$query_list_file") or die "$PATHDATA/$query_
+list_file: $!\n";
chomp( my @query_arr = <HH> );
close HH;

my $query_regex = join( '|', @query_arr );

open(XX, "<", "$PATHDATA/$file_to_search") or die "$PATHDATA/$file_to_
+search: $!\n";
open(DD, ">", "$PATHDATA/query_results.txt") or die "$PATHDATA/query_r
+esults.txt: $!\n";
my $count=0;

while ( <XX> ) {
    if ( /^($query_regex)\]/ ) {
        print DD "############\nQUERY: $1\nMATCH: $_\n";
        $count++;
    }
}
print DD "Entrate trovate: $count\n";

[download]
(In addition to allowing for other input files and using a single regex to check all matches, I also left out the "debug" stuff, rearranged the output format a little, and changed the "open" statements to use the 3-arg style.) UPDATED to add "or die ..." on each of the "open" statements -- that should be a habit.

If you still have a problem when using some small test files, post a complete and runnable script (like the one shown here) with the test data.

In reply to Re^3: Sort of basic search engine/pattern matching problems by graff
in thread Sort of basic search engine/pattern matching problems by bvulnerbility

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.