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-pkg-inplace.o","ghc-pkg.e
   
xe","main.exe","Main.hi","Main.hs","Main.hs.diff","Main.o","Makefile","tst-glob.
   
exe","tst-noglob.exe","tst.c","tst.hi","tst.hs","tst.o","Version.hi","Version.hs
   ","Version.o"]

   C:\fptools\ghc\utils\ghc-pkg>tst-noglob *
   ["*"]

   C:\fptools\ghc\utils\ghc-pkg>tst-glob '*'
   ["'*'"]

   C:\fptools\ghc\utils\ghc-pkg>tst-noglob '*'
   ["'*'"]

it does, however, explain why one often has the feeling
of having to fight two levels of globbing when using ghc
compiled code under cygwin bash - that does seem to
be exactly what is happening (note how quoting changes
the globbing results instead of preventing globbing!-(

   $ ./tst-glob *
   
["Main.hi","Main.hs","Main.hs.diff","Main.o","Makefile","Version.hi","Version.hs","Version.o","ghc-p
   
kg-inplace.exe","ghc-pkg-inplace.hi","ghc-pkg-inplace.hs","ghc-pkg-inplace.o","ghc-pkg.exe","main.ex
   e","tst-glob.exe","tst-noglob.exe","tst.c","tst.hi","tst.hs","tst.o"]

   $ ./tst-noglob *
   
["Main.hi","Main.hs","Main.hs.diff","Main.o","Makefile","Version.hi","Version.hs","Version.o","ghc-p
   
kg-inplace.exe","ghc-pkg-inplace.hi","ghc-pkg-inplace.hs","ghc-pkg-inplace.o","ghc-pkg.exe","main.ex
   e","tst-glob.exe","tst-noglob.exe","tst.c","tst.hi","tst.hs","tst.o"]

   $ ./tst-glob '*'
   
[".depend",".depend.bak",".ghc-pkg-inplace.hs.swp",".Main.hs.swp","ghc-pkg-inplace.exe","ghc-pkg-inp
   
lace.hi","ghc-pkg-inplace.hs","ghc-pkg-inplace.o","ghc-pkg.exe","main.exe","Main.hi","Main.hs","Main
   
.hs.diff","Main.o","Makefile","tst-glob.exe","tst-noglob.exe","tst.c","tst.hi","tst.hs","tst.o","Ver
   sion.hi","Version.hs","Version.o"]

   $ ./tst-noglob '*'
   ["*"]

any suggestions on how to deal with this?
claus


_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc

Reply via email to