On Fri, Dec 19, 2003 at 04:51:50PM +, MR K P SCHUPKE wrote:
> Whilst I appreciate the topic of show is not directly related to GHC,
> what I would like to know is how to handle UNICODE properly... If I assume
> I have a good unicode terminal, so stdin and stdout are in unicode format,
> and all
I'm getting problems building ghc 6.2. It fails building the
documentation (which I didn't really want anyway). I'm using the gentoo
ebuild script.
I've got haddock 0.6 installed. (That was my first error!)
I'm hoping someone might know what is going wrong here. I'll report back
to the gentoo ghc
MR K P SCHUPKE wrote:
The problem is that if you are reading single bytes, 233 is
not necessarily é.
Erm, Internationalisation is not my thin as such... but I can't help
commenting that from a systems point of view this is an utterly bad
sitiation to be in... I though Haskell used unicode? I
Whilst I appreciate the topic of show is not directly related to GHC,
what I would like to know is how to handle UNICODE properly... If I assume
I have a good unicode terminal, so stdin and stdout are in unicode format,
and all my text files are in unicode, how do I deal with this properly in
GHC.
This is ghc-6.2, trying to built it with ghc-6.2:
$ ./configure --with-x --enable-threaded-rts --enable-objectio
--enable-hopengl
=>
[...]
==fptools== make all -wr;
in /home/cm/Desktop/ghc-6.2/libraries/ObjectIO
>The problem is that if you are reading single bytes, 233 is
>not necessarily é.
Erm, Internationalisation is not my thin as such... but I can't help
commenting that from a systems point of view this is an utterly bad
sitiation to be in... I though Haskell used unicode? I thought in unicode
the id
Thanks for your reply. I'm afraid it's left me even
more confused about which way to go with this :-(
If it's possible that future Haskell FFI's don't guarantee
that all finalisers are run then this more or less rules
out the use of the reference counting solution (which
wasn't particularly attrac
This discussion is getting a little out of hand ;-)
An instance of Show should (but doessn't have to):
- generate a rendering of its argument as a String that
(a) follows the Haskell lexical syntax, and
(b) with an appropriate instance of Read can reconstruct the
ori
rmartine:
>
>
>
> On Fri, 19 Dec 2003, Donald Bruce Stewart wrote:
>
> > This is an unregisterised build, with profiling libs, no docs and no GHCi.
> >
> > The mips64 port requires an external libgmp. This should come installed
> > with the "freeware" packages for Irix.
> >
>
> - And set your
On Fri, 19 Dec 2003, Donald Bruce Stewart wrote:
> This is an unregisterised build, with profiling libs, no docs and no GHCi.
>
> The mips64 port requires an external libgmp. This should come installed
> with the "freeware" packages for Irix.
>
- And set your LD_LIBRARY_PATH variable properly:
Hello,
> What I don't understand is why you want show for this. As I
> mentioned earlier, to output strings and get accented
> characters, all you have to do is to output the string with
> putStr, and voilà, les signes diacritiques.
Sometimes, I want to do cheap and dirty test programs that "show
11 matches
Mail list logo
