Re^2: using wildcard character * in perlscript command line

Replies are listed 'Best First'.
Re^3: using wildcard character * in perlscript command line by shenme (Priest) on Jan 28, 2005 at 15:56 UTC
Because glob() will simply pass-thru anything that doesn't need expansion, otherwise it would lose ordinary filenames. But if the 'option' might have the expandable characters '*' or '?' you will be in danger of losing _those_ options. glob('-f?') returns nothing (usually), though glob('-f') will simply return '-f'.	[reply]
Re^3: using wildcard character * in perlscript command line by BrowserUk (Patriarch) on Jan 28, 2005 at 15:57 UTC
If the value passed to glob doesn't contain a wildcard, it is passed through untouched. `P:\test>perl -wle" print for glob '-debug' " -debug` [download] As for the why, if there is no file of that name existing, you'll need someone with the historical perspective (merlyn?). Maybe, just so that it doesn't affect non-wildcard parameters? Examine what is said, not who speaks. Silence betokens consent. Love the truth but pardon error.	[reply] [d/l]
Re^3: using wildcard character * in perlscript command line by Aristotle (Chancellor) on Jan 28, 2005 at 17:25 UTC
Perl's glob was originally implemented in terms of csh's. From `man csh`: If a word contains any of the characters , ?, [ or { or begins with the character ~ it is a candidate for filename substitution, also known as globbing. If you use the `bsdglob` function from File::Glob (which is how glob is implemented nowadays), you can pick behaviour as desired. Makeshifts last the longest.*	[reply]
Re^3: using wildcard character * in perlscript command line by blazar (Canon) on Jan 29, 2005 at 08:29 UTC
For the same reason for which (depending on an option, really) *NIX shells (well, at least bash that I know) pass through any unmatched item.	[reply]