On Oct 26, 2009, at 20:12 , Richard O'Keefe wrote:
On Oct 25, 2009, at 5:01 PM, Curt Sampson wrote: The corresponding part of the GHC documentation says
GHC assumes that source files are ASCII or UTF-8 only, other encodings are not recognised. However, invalid UTF-8 sequences will be ignored in comments, so it is possible to use other encodings such as Latin-1, as long as the non-comment source code is ASCII only.
There's no obvious reason why GHC couldn't support any source encoding that the host's iconv() supports.
That would be the Haskell98 Report: Haskell uses the Unicode [11] character set. However, source programs are currently biased toward the ASCII character set used in earlier versions of Haskell . This syntax depends on properties of the Unicode characters as defined by the Unicode consortium. Haskell compilers are expected to make use of new versions of Unicode as they are made available. So yes, it's reasonable to "blame" the language (spec). -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH