Re^5: Portability of glob function in a modern perl

The hint Don't count on filename globbing is meant short for Don't count on that all glob parameters on the command line will have been expanded by the calling shell for you, because, on Win32 (and likely VMS), the shell doesn't expand glob filespecs.

This is unrelated to the glob builtin, which "works" within the boundaries already given. The usage of File::Find and File::Find::Rule is still recommendable over manual reading or globbing via glob, because glob (and File::Glob) live under the assumption that whitespace is a sensible delimiter for glob patterns.

Comment on Re^5: Portability of glob function in a modern perl

Replies are listed 'Best First'.
Re^6: Portability of glob function in a modern perl by Anonymous Monk on Aug 12, 2005 at 15:52 UTC
Don't count on that all glob parameters on the command line will have been expanded by the calling shell for you, I seriously doubt that the quoted warning means that. I think the warning means you ought to use `opendir/readdir/closedir` instead of calling `glob`. Expansion of parameters by the shell (and Unix shells do more expansion that just '*') is the responsibility of the caller - (s)he decides whether or not to call something via the shell or not.	[reply]
Re^6: Portability of glob function in a modern perl by ccn (Vicar) on Aug 12, 2005 at 10:42 UTC
because, on Win32 (and likely VMS), the shell doesn't expand glob filespecs. That became obsolete since the `glob` emulates chs behavior regardless OS. Isn't it?	[reply] [d/l]
Re^7: Portability of glob function in a modern perl by Corion (Patriarch) on Aug 12, 2005 at 10:47 UTC
No. Compare the output of the following snippet on Win32 with `cmd.exe` as the shell and with (say) `bash.exe` as the (non-default) shell: `perl -le "print for @ARGV" ` [download] On Win32 / `cmd.exe`, this will output: `Q:\>perl -le "print for @ARGV" ` [download] So, obviously, no globbing has taken place. Under the `bash` shell, it outputs a listing of a lot of files, because I started it in a directory with a lot of files: `bash-2.05b$ perl -le "print for @ARGV" 44pruefung.py ABGLSAPFIOP.TXT.200405261836 Opics_MurexGD_SapFi.20040526.csv abgleich-MurexGD-SapFi.py abgleich-Opics-MurexGD-SapFi-andere-Konten.py abgleich-Opics-SapFi.py abgleich.py abtest.py go.sh murex_salden_20040526.fi mx_fxdpos_20040526 opics_kassa_20040526.fi opics_termin_20040526.fi ssd_20040526.fi` [download] This is the difference between the two shells calling Perl, and there is no hidden magic in Perl to unglob stuff.	[reply] [d/l] [select]