Simon Marlow [EMAIL PROTECTED] writes:
It's intentional, but it can be easily turned off. Do people want to
see feature-requests, task-list entries and so forth on this mailing
list, or should they be confined to, say, [EMAIL PROTECTED]
I would vote to put them in a separate list. At least
On 19 January 2005 05:31, John Meacham wrote:
A while ago I wrote a glibc specific implementation of the CWString
library. I have since made several improvements:
* No longer glibc specific, should compile and work on any system with
iconv (which is unix standard) (but there are still
On 18 January 2005 21:01, William Lee Irwin III wrote:
On 15 December 2004 14:46, William Lee Irwin III wrote:
There seems to be some trouble with the debian ghci on sparc64. I
can dredge up more information if given an idea of what to look for.
On Tue, Jan 18, 2005 at 04:41:02PM -,
Good point, thank you! I'd forgotten that the OGI modules paper, which I
read carefully at the time, covered recursion (Section 5.4).
But my real point wasn't that it's impossible to define a meaning, only
that the meaning might be a bit unexpected to a programmer, and involves
a fixpoint
On 17 January 2005 22:53, Sean Bowman wrote:
I'm trying to install HUnit to use with ghci and hugs and having some
trouble. It works if I use the -i option with ghci, but I'd rather
not have to specify that on the command line every time. Putting it
in a ~/.ghci file doesn't seem to work.
Question regarding implicit parameters... The GHC manual says:
Dynamic binding constraints behave just like other type class
constraints in that they are automatically propagated.
But the following code produces an error:
Hello,
I would like to port GHC to Arm so that I can compile Haskell programs
for use on my Zaurus or in Debian's ARM port.
I have talked to Ian Lynagh about this, and he believes that there was
some sort of problems with floats. I don't know exactly that was, if it
was in gcc or ghc, or if it
Isn't it just the monomorphism restriction at work?
This works fine:
f () = do
a - get_unique
putStr (showInt a \n)
b - get_unique
putStr (showInt b \n)
c - get_unique
putStr (showInt c \n)
Yes, adding -fno-monomorphism-restriction allows the example to compile.
I guess I got confused by the error message, expecting it to mention the
monomorphism restriction directly... I'm sure it does sometimes. Any
chance of improving the error message for this?
Jorge Adriano Aires wrote:
Isn't it
