[PATCH] Better encoding/decoding for GHC
batterseapower at hotmail.com
Tue May 24 18:52:23 CEST 2011
On 24 May 2011 02:16, Ian Lynagh <igloo at earth.li> wrote:
> On Wed, May 18, 2011 at 11:14:08PM +0100, Max Bolingbroke wrote:
>> On 18 May 2011 22:54, Mark Lentczner <mark.lentczner at gmail.com> wrote:
>> > The range is U+EF80 through U+EFFF, called "Reserved for encoding hacks".
>> OK, I've applied another patch so we match this.
> So how do I fix the "rm a*" program below now? (if there are some docs
> somewhere explaining it, please just point me at them).
This program should work unmodified. The fact that it doesn't
demonstrates that I need to replace some instances of the
Foreign.C.*CString functions with their escape-handling counterparts
(withFilePath and friends). Although I fixed this in some libraries I
apparently forgot to do so in others.
Alternatively, I could change the Foreign.C functions to do the Right
Thing with escape characters. This would strictly be in violation of
the FFI spec though it would make it vastly more probable that 3rd
party libraries would work correctly with strings containing
More information about the Cvs-ghc