[nhc-bugs] Building nhc98 on Windows 2000

[Sigbjorn Finne]

"Malcolm Wallace" <Malcolm.Wallace@cs.york.ac.uk> writes:
> "Sigbjorn Finne" <sof@galois.com> writes:
>
> > > /tmp/... directory *does* exist, but the \tmp\... directory does not.
> > > (And indeed, why should it, since the invocation didn't ask for it?)
> >
> > Notice that both GHC and the mingw system calls (the MS provided
> > C runtime functions, really) are capable of understanding paths that
> > contain either "/" or "\" as directory separators, so you're reading too
> > much into the slashes being reversed in that output message.
>
> So am I right in thinking that if GHC did no internal filepath mangling
> whatsoever, everything file-related would just work?
>

Sigh, I thought we'd gone through this before...that's got nothing to do
with it - you really should try to stop being so paranoid about the
direction
of those slashes, Malcolm! :)

The story is if I feed GHC a file path that can only be interpreted
correctly
wrt. a particular application / DLL, GHC will necessarily have problems.
Examples include paths that need to be resolved by cygwin's implementation
of open(), URLs that need to be interpreted/resolved by a web browser etc.

To repeat, this is not a slash-direction issue -- for the case in point, the
path
could only be resolved by consulting the cygwin mount table for /tmp.


--sigbjorn