very interesting indeed! This is the first time I read something like this on the argument and you will pardon my ignorance on the whole matter.

> The C runtime library then interprets that string to find argc and build argv to pass to main

Given your precious hint I discovered perlwin32#Using-perl-from-the-command-line documentation. But let me see if I understood it right.

The above document says:

> It is particularly important to note that neither the shell nor the C runtime do any wildcard expansions of command-line arguments

and the above sounds different from your statement "Wildcard expansion ... is therefore a function of the runtime libraries perl and raku are linked against".

But what you said seems confirmed by some experiment: yesterday I chatted a bit on the #raku channel on irc and someone said they noticed opposed behaviour on windows, with and without expansion, probably due to different build of the raku itself, rakubrew iirc.

So the above document (related to perl but I suppose is valid for raku too) seems to be incorrect in the sense that sometimes perl or raku can be built using a C runtime library that effectively does the expansion? Can be this the case of the OP?

If the above is true then can be perl built on windows using a C runtime library that is able to expand the * char as done by more smart shells? This would be a nice improvement.

Thanks for your contribution

L*

I don't have Raku so I tested against Perl.

Looks like only doublequotes are stripped if not escaped.

D:\tmp\pm>perl -e"print @ARGV" *
*
D:\tmp\pm>perl -e"print @ARGV" '*'
'*'
D:\tmp\pm>perl -e"print @ARGV" "'*'"
'*'
D:\tmp\pm>perl -e"print @ARGV" "*"
*
D:\tmp\pm>perl -e"print @ARGV" \*
\*
D:\tmp\pm>perl -e"print @ARGV" \"*\"
"*"
D:\tmp\pm>
[download]