Re: Re (tilly) 2: Sort of like a file handle, but not

I beg to differ (about Windows). Run this at a command prompt:

C:\> perl -e "print map( \"$_\n\", glob(\"{A,B}{a,b}\"))"
[download]

For this particular example, I get identical results on Windows to that on UNIX. Note that Windows' braindead command line quote handling, or lack thereof, requires escaping the double quotes in the perl code and surrounding the entire thing with double quotes

Under Windows, each executable must do its own command-line globbing, Perl, like any Windows executable must then expand wildcards on its command line, which it seems to do by calling the standard Microsoft __setargv routine, which is far less powerful than even csh in terms of globbing.

On the other hand, the internal glob() routine is implemented specially for Windows, to behave like a UNIX shell. At least it is in ActiveState's Perl.

Cheers,
dmm

Just call me the Anti-Gates ...

Comment on Re: Re (tilly) 2: Sort of like a file handle, but not Download Code

Replies are listed 'Best First'.
Re (tilly) 4: Sort of like a file handle, but not by tilly (Archbishop) on Aug 22, 2001 at 01:38 UTC
Before begging too much, run: `perl -v` [download] As I stated, I find that the output differs between Perl 5.005_03 on Windows and Linux. On Windows I get nothing. On Linux I get 4 lines. Now the odds are that you have a recent Perl. That means either a heavily patched 5.005 or (more likely) you have 5.6. In that case see the other notes in this thread about the glob implementation changing. In short, before saying someone's statement (made on a direct test) is wrong, it is good to have tied out all relevant factors. And in this case you can see that while it may not differ for you, it does for me. And it does for me on the version that I stated up front had differences. Incidentally I already knew about the braindead command line handling on Windows. If you want to prove that the executable handles it, it is probably easiest to just write a trivial VB application that echoes the command line. And the best way around the way that perl.exe handles it is to pick a different quote delimiter: `perl -e "print map qq($_\n), glob('{A,B}{a,b}');"` [download]	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re (tilly) 4: Sort of like a file handle, but not
by tilly (Archbishop) on Aug 22, 2001 at 01:38 UTC

perl -v
[download]

Now the odds are that you have a recent Perl. That means either a heavily patched 5.005 or (more likely) you have 5.6. In that case see the other notes in this thread about the glob implementation changing.

In short, before saying someone's statement (made on a direct test) is wrong, it is good to have tied out all relevant factors. And in this case you can see that while it may not differ for you, it does for me. And it does for me on the version that I stated up front had differences.

Incidentally I already knew about the braindead command line handling on Windows. If you want to prove that the executable handles it, it is probably easiest to just write a trivial VB application that echoes the command line. And the best way around the way that perl.exe handles it is to pick a different quote delimiter:

perl -e "print map qq($_\n), glob('{A,B}{a,b}');"
[download]

[reply]
[d/l]
[select]