Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
Hey All! I know that when you call File::Find::find(\&wanted,"/foo/bar");, the find() function passes some stuff to the wanted() function that it uses internally.

My question is, how do I pass data to the wanted() function without having it complain? Here is a small snippet of code I tried that attemps to pass two filehandles to the wanted() function:
while (<MAINDB>) { find(\&wanted(\*C_LOG, \*R_LOG), $_); }
MAINDB is just a DB of directories to search, and C_LOG and R_LOG are simply two log files that program data needs to print to. However, when I try this, I get this message:
Not a CODE reference at C:/Perl/lib/File/Find.pm line 432, <MAINDB> line 1.
I am assuming that this is dealing with the \&wanted function call and also assume that it is complaining because I tried to pass parameters to it - any thoughts on why this is happening?

P.S. Here is my wanted() function:
sub wanted { my $clog_filehandle = shift; my $rlog_filehandle = shift; # $_ is file name (File::Find thing) my $file = $_; print "In wanted(), checking $file...\n"; copy_file( $file, $clog_filehandle, $rlog_filehandle) if (-f $f); }
Pretty simple - just checks if the file is actually a file (not a directory or something else) and if so calls copy_file([filename],[filehandle1],[filehandle2]); Guess that wasn't exactly a short question, but it should be quick work for my fellow monks who are much more intelligent than I! Thanks a ton!

r. j o s e p h
"Violence is a last resort of the incompetent" - Salvor Hardin, Foundation by Issac Asimov

In reply to Quick File::Find Question by r.joseph

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.