Hi nirelit,

Any ideas on how would you approach this?

One way is to use the core module File::Find, you can get the full filename of each found file from the variable $File::Find::name, and use File::Spec's splitdir to split the filename into its components. The reverse index could be done with a hash, assuming there's enough memory for all the entries to fit in.

That's just one way, there are also the modules File::Find::Rule, Path::Class, or Path::Tiny, but the above has the advantage that it uses only core modules. The advantage of Path::Class and Path::Tiny is that they also have methods built in to slurp the files, which would make creating your index files a little bit easier.

Hope this helps,
-- Hauke D

In reply to Re: creating an index of files contents by haukex
in thread creating an index of files contents by nirelit

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.