Claus Reinke wrote:
but that does seem to be a bug in ghc-pkg-inplace.hs,
so perhaps that should be fixed first, and then we could use '*'
instead of '.' (even though it isn't full globbing, '*' is only
interpreted at string ends).
the problem is not specific to ghc-pkg-inplace, but is
shared
So different commands can (and do) have different quoting and globbing
semantics. Great huh?
it does have its advantages, though. as i'm implementing a package
globbing, i'd like to avoid file globbing being applied to these same
parameters.
We could have a -no-globbing link-time option, but
./main '*' -- this does not protect from globbing!
"*" works afair. if you want to disable globbing completely, link it
with gcc-lib\CRT_noglob.o (at least this works with 6.4-6.6)
'*' works for cygwin bash
"*" works for win32-self-globbing programs in cmd.exe
but how do you protect * from
Hello Simon,
Friday, November 16, 2007, 12:31:05 PM, you wrote:
>> the problem is not specific to ghc-pkg-inplace, but is
>> shared by all ghc mingw programs using getArgs:
>>
>>./main '*' -- this does not protect from globbing!
"*" works afair. if you want to disable globbing completely, l
unfortunately, disabling mingw globbing is not the solution,
as it leaves no globbing at all under cmd.exe:
C:\fptools\ghc\utils\ghc-pkg>tst-glob *
[".depend",".depend.bak",".ghc-pkg-inplace.hs.swp",".Main.hs.swp","ghc-pkg-inpla
ce.exe","ghc-pkg-inplace.hi","ghc-pkg-inplace.hs","ghc-pk
but that does seem to be a bug in ghc-pkg-inplace.hs,
so perhaps that should be fixed first, and then we could use '*' instead of '.' (even though it
isn't full globbing, '*' is only interpreted at string ends).
the problem is not specific to ghc-pkg-inplace, but is
shared by all ghc mingw prog
