1. =foreach needs to be foreach. You have made a syntax error that makes the interpreter think you are entering a documentation mode (see perlpod), thus no useful error message.
2. Rather than <*>, which operates as a glob, you mean <>, which reads off STDIN.

@files = <>;
chomp @files; # Since there are trailing newlines
foreach $file (@files) {
    if (-f $file) {
        print "This is a file: " . $file."\n";
    }
    if (-d $file) {
        print "\n\nThis is a directory: " . $file."\n";
    }
}
[download]

use strict;
use warnings; 

my @files = <>;
chomp @files;
foreach my $file (@files) {
    if (-f $file) {
        print "This is a file: $file\n";
    }
    if (-d $file) {
        print "\n\nThis is a directory: $file\n";
    }
}
[download]

Update: Corrected omitted chomp.

Sorry, but have you run your code? I ran it and on entering path name after running my perl script it says :

C:\Perl64\bin>perl t1.pl C:\Perl64\bin
Can't do inplace edit: C:\Perl64\bin is not a regular file at t1.pl li
+ne 20.
[download]

Ahh, so you do not intend STDIN, but rather @ARGV for your input. In that case, you might use

use strict;
use warnings; 

foreach my $file (@ARGV) {
    if (-f $file) {
        print "This is a file: $file\n";
    }
    if (-d $file) {
        print "\n\nThis is a directory: $file\n";
    }
}
[download]

#11929 First ask yourself `How would I do this without a computer?' Then have the computer do it the same way.

Can't do inplace edit: C:\Perl64\bin is not a regular file at t1.pl line 20.

How can you possibly be getting a error on line 20 of kennethk's code, when neither version of the code he posted has 20 lines?

---

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?

How about something like this:

#!/usr/bin/perl

use warnings;
use strict;

use File::Find;

my $path;

if ( $ARGV[0] ){
    $path = $ARGV[0];
}
else {
    print "Enter path: ";
    chomp (my $path = <STDIN> );
}

find( \&wanted, $path );

sub wanted {
    print "File: $_\n" if -f;
    print "Dir:  $_\n" if -d;
}
[download]

Output:

steve@ubuntu:~/devel/repos/scripts/file_find$ ./find.pl 
Enter path: test
Dir:  .
File: b.txt
File: a.txt
Dir:  .hidden
Dir:  a
Dir:  b
[download]

Update: Fixed so it allows either a command line arg, and if not present, prompts the user for the path.

Update2: This code actually seems broken since I made the first update, but I don't have time to look at the issue. This is an informational warning only, until I get a chance to look closer.

C:\Perl64\bin>perl t1.pl Enter path: C:\Perl64\bin Undefined subroutine &main::find called at t1.pl line 18, <STDIN> line 1. :( While I got the solution :

$dir =<>;
chomp($dir);
opendir DIR, $dir or die "cannot open dir $dir: $!";
my @file= readdir DIR;
print @file;
closedir DIR;
[download]

UPDATE: I tried with almost all the codes and most of them are working fine along with what I have pasted here. But the issue is that for some complex path it's not working.

Post the contents of the script. My 'find' line is on line 18, not 23.

print "enter path\n";
$path = <>;
chomp($path);
opendir (DIR, $path) or die $!;
while (my $file = readdir(DIR)) {
    if(-f $file) {
        print "this is a file--->".$file."\n";   
    }           
}
closedir(DIR);
[download]

#!/usr/bin/perl

use 5.10.0;
use strict;
use warnings;

print "Enter a directory: ";
chomp(my $dir = <>);
$dir =~ s!(/|\\)$!!;

while (my $entry = <$dir/*>) {
    my $type = -f $entry ? 'a file'
                         : -d $entry ? 'a dir'
                                     : 'unknown';
    say "$entry is $type";
}
[download]

use strict;
use warnings;

my @files = `dir /b`;
foreach(@files){
    chomp($_);
    print $_."\n";
}
[download]