I have implemented your function and added a few things from the code above including Cody Pendent's /\s+/ suggestion. I should have thought of these myself since I have done similar stuff in the past.

The resulting Storable file is only a few thousand K more than my original text index file. Now all I need to do is implement a searcher. I may re-write this into an object structure for ease of maintence at some point but I like the way things are headed. I still need to add the stop list in a hash but I have some obligations I need to take care of today. I have appended the code with my changes below.

I still have one more question however. Why do I need so many chdir functions? It seems unable to deal with "\..\index" or any of that sort of stuff. Thanks again!

use strict; use warnings; use utf8; use Storable; chdir "texts"; my @files = glob "*.txt"; my %file_idx = map {; $_ => index_file( $_, 5 ) } @files; chdir "\.."; chdir "index"; store \%file_idx, "text.idx"; =pod { 'foobar.txt' => { word => [ 1, 3, 5, 6 ], another => [ 5, 7, 2, ] }, 'barfoo.txt' => { ....... } =cut sub index_file { my $filename = shift; my $lines_of_context = $_[0] > 0 ? shift() : 1; open my $fh, "<", $filename or die "Couldn't open $filename: $!"; my @offsets; my %index; while ( my $line = <$fh> ) { push @offsets, tell $fh; my $offset = scalar( @offsets ) < $lines_of_context ? $offsets[0] : shift @offsets; for my $word ( split /\s+/, $line ) { $word = lc $word; $word =~ s/,$|\.$|\[|\]|\(|\)|;|:|!//g; if(&inStopList($word)) { next; }elsif($word =~ /p\.(\d)+/) { next; }elsif($word =~ /\-{5,}?/) { next; } push @{ $index{$word} }, $offset; } } close $fh or warn "Couldn't close $filename: $!"; return \ %index; } sub inStopList { my $word = shift; my @stopList = ("the", "a", "an", "of", "and", "on", "in", "by", " +with", "at", "he", "after", "into", "their", "is", "that", "they", "f +or", "to", "it", "them", "which"); foreach my $stopWord (@stopList) { if($word eq $stopWord) { return $word; } else { next; } } }

In reply to Re: Re: Re: Re: Simple Text Indexing by cyocum
in thread Simple Text Indexing by cyocum

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.