I have found numerous pages that point to the documentation for File::Find and state that preprocess and follow are essentially not compatible. I have looked at the source code for File::Find and have seen that they are indeed kept separate for some reason. What I have yet to find is one explanation of WHY they are mutually exclusive.

Does such a statement exist?

If not, what do you think the chance is for File::Find to be updated to allow the two to coexist? (It would probably be done by adding another configuration parameter, since it might break existing code to simply turn on preprocess functionality across the board.) It seems that File::Find's current design in this regard has existed for quite some time. (Again: why?)

Any insights are appreciated.

In reply to Why is preprocess a no-op when follow is true for File::Find? by bounsy

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.