Re^2: ARGV *.* importing problems

[choroba]

Also see the built-in glob, but this can have issues with whitespace, so File::Glob is usually safer.

Safer? In the documentation you linked it says: Beginning with v5.6.0, this operator is implemented using the standard File::Glob extension.

[cdarke]

While it is true that the documentation says that, consider:

my @files = glob('C:/Program Files/*');
print "@files\n";

gives:

C:/Program

whereas:

use File::Glob qw(glob);
my @files = glob('C:/Program Files/*');
print "@files\n";

gives:

C:/Program Files/7-Zip C:/Program Files/ATI C:/Program Fil...

etc. ad nauseum.
This on ActiveState perl 5.12.3 64-bit Windows 7, but has been the same siince at least 5.6.0. I get similar results on Linux on 5.8.8.

[choroba]

The documentation also says

See File::Glob for details

And if you do, you can see this:

  ## override the core glob (CORE::glob() does this automatically
  ## by default anyway, since v5.6.0)
  use File::Glob ':globally';
  my @sources = <*.{c,h,y}>;

But this piece of code does not behave like File::Glob::glob (namely, it does not call bsd_glob instead of glob). The question is: What exactly does CORE::glob automatically since 5.6.0 then?

[cdarke]

Good point, but this brings us back to my original comment that File::Glob is safer. Whether that is how it should be is another question altogether.