Context Navigation

Ticket #113
(closed enhancement: fixed)

Use CAString FFI functions instead of CString ones

Reported by:

batterseapower

Owned by:

Priority:

minor

Milestone:

Version:

Keywords:

Cc:

Description

Haskeline uses Foreign.C.String.*CString to marshal locale names. Locale names will always be encoded in ASCII, so it would probably be prudent to use the *CAString variants instead to prevent use of the locale encoding from screwing things up.

Attached patch achieves this.

Attachments

Change History

Thanks for the patch! Out of curiosity, do you know of any pending plans to switch over the Foreign.C.String functions to use the locale's encoding? (My understanding is that currently the CString and CAString functions behave the same.)