Geetings, witandhumor!
After running your code on my Win32 machine, I received the same (or a similar) error about permissions. A few well placed print statements and switches flipped later, I found that File::Find was finding the . file/directory first. The open is the part that seems to fail when it attempts to open the . file/directory.
I did a few file tests ( -r and -f) to find only readable plain files. This happily skips over the . and .. files/directories.
Here's code that does not get the same file permission error:
#!c:\perl\bin\perl.exe -w
use strict;
use File::Find;
use Carp;
#variables
my ($directory,$file,$text);
print "Enter search text: ";
$text = <STDIN>;
chomp $text;
$directory = 'c:\my_directory';
find (\&search,$directory);
sub search {
my $file = $File::Find::name;
if (-r $file && -f $file) {
open (FILE, "$file") or carp "Guess what, it didn't work!\n$!";
my $line = <FILE>;
close FILE;
print "$text - $file"
if $line =~ /$text/;
}
}
Hope this helps!
- Daruma
-
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.
|