Front page | perl.perl5.porters |
Postings from March 2006
On Thu, Mar 23, 2006 at 02:03:57PM +0100, Rafael Garcia-Suarez wrote:
> Tom Hukins (via RT) wrote:
> > Fatal.pm and readdir() do not play well together. Run the following
> > script in a directory containing several files. It only prints out '.'.
> > Then comment out the 'use Fatal' line and run the script again. It now
> > prints out all the files in the directory.
> >
> > #!/usr/bin/perl
> >
> > use strict;
> > use warnings;
> >
> > use Fatal qw(readdir);
> >
> > my $start_dir = '.';
> > opendir(my $dir, $start_dir);
> > my @subdir = readdir $dir;
> > closedir $dir;
> > print "@subdir\n";
>
> Fatal will replace readdir() by this function :
>
> sub (*) {
> local($", $!) = (', ', 0);
> CORE::readdir($_[0]) || croak "Can't readdir(@_): $!";
> }
>
> As you see, this construct forces readdir to be called in scalar
> context; which is why it returns only one element, as documented
> in perlfunc.
>
> We could add a wantarray() before that, but that would alter the proper
> behaviour of other weird code like this :
>
> use Fatal qw(open);
> my @useless_array = open my $fh, "non-existent-file";
>
> Other ideas ?
*Is* there any way to detect a failed list-context readdir()? If not,
Fatal should continue to do what it is doing and the limitation should
be documented.
Thread Previous
|
Thread Next