Hi, Discipulus, I meant that in these 3 cases:
perl -e "print join qq(\n), @ARGV" * pp -e "print join qq(\n), @ARGV" -o printargv.pl -P && perl printargv. +pl * pp -e "print join qq(\n), @ARGV" -o printargv.par -p && par printargv. +par *
the executable, being finally loaded and run, is one and the same perl.exe. Its main function is loaded/executed by wrapper/loader created by/in MinGW environment, being present at the time Strawberry Perl was built. The _CRT_glob appears to be responsible for glob expansion of arguments -- i.e. main gets not real argv, but expanded (or not) by wrapper. Just as in C example in my comment above.
Whereas, in
pp -e "print join qq(\n), @ARGV" -o printargv.exe && printargv.exe *
the loaded executable is fresh, just compiled printargv.exe, whose main is also loaded by wrapper/loader, and its compilation somehow missed the state of _CRT_glob flag.
As to Strawberry's idea of providing MinGW/gcc environment for CPAN distributions to install "same as in Linix/Unix", -- no other way for that to work but to have Perl compiled in the same MinGW/gcc environment, no?
In reply to Re^3: PAR pp glob for me on windows?
by vr
in thread PAR pp glob for me on windows?
by Discipulus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |