On 20 Οκτ 2009, at 3:08 μ.μ., Simon Marlow wrote:

It's not to do with Haskeline. The real underlying problem is that our filesystem APIs on Unix interpret FilePath as [Word8] without doing any encoding/decoding; they just strip off all but the low 8 bits of each Char. This is a long-standing problem, and won't be solved properly until we switch to an abstract FilePath type, but that's a big change that will break lots of code.

Lots more good discussion here:

http://hackage.haskell.org/trac/ghc/ticket/3456

If there were a filePathToString function we could use it in GHC to fix the above glitch.

Cheers,
        Simon

Understood. Thank you very much for the pointer and your response.

--
C. Chryssochoidis_______________________________________________
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users

Reply via email to