Manuel M T Chakravarty [EMAIL PROTECTED] wrote,
I am pleased to announce version 0.10.16 Altocumulus
Stratiformis Perlucidus Undulatus of the C interface
generator C-Haskell.
The web site
http://www.cse.unsw.edu.au/~chak/haskell/c2hs/
now also has a binary rpm that is compiled
For parallel Haskell you need the GPH mailing list, not
Glasgow-haskell-users.
You can find details of that list at
http://www.cee.hw.ac.uk/~dsg/gph/
Meanwhile, you're suffering from a compiler version shift: the new
compiler can't read the old compiler's Foo.hi files.
Just rm *.hi
Thanks for the pointer. I still get the following error, when I do gmake.
echo '#!/bin/sh' ghc-inplace
echo exec /root/fptools/ghc/compiler/ghc-5.05 '-B/root/fptools' '$@'
ghc-inplace
chmod 755 ghc-inplace
I'd settle for that kind of indiscriminate flushing -- as is,
trivial I/O examples such as
main = do
putStr What is your name?
ls - getLine
putStrLn (Hello ++ ls ++ !)
fail to behave as expected.
That depends on what you expect... :-) The Haskell report says nothing
about
I have seen this before and it puzzled the hell out of me too.
To be honest I have forgotten the exact cause, but it's something to do
with the fact that you haven't done a new 'autoconf' or a new
'configure' or something.
Much the easiest thing is to start from scratch. Check out an entirely
I agree, I certainly don't want inefficency introduced by unecessary
flushes, and
I would expect to control where the flushes happen. I think the query
originally
assumed a sequencing ambiguity in the IO monad... but in my experiance
(all be it
limited) the IO monad is there to ensure strict
Hello glasgow-haskell-users,
First, it would be good to have examples somewhere around ObjectIO
main page. I've figured out how to download source code for examples
only after third or fourth try.
I know, that the question about examples and source code should be
directed to the
Simon Marlow [EMAIL PROTECTED] writes:
I'd settle for that kind of indiscriminate flushing -- as is,
trivial I/O examples such as
main = do
putStr What is your name?
ls - getLine
putStrLn (Hello ++ ls ++ !)
fail to behave as expected.
That depends on what you
The previous impl had facilities for controlling this - you
could label handles
as being connected (i.e., read() on one caused flushes on the
other.) By
default, stdin was connected to stdout and stderr. If that
turned out to
be troublesome, the connection could be broken (I could be
Simon Marlow wrote:
I'd settle for that kind of indiscriminate flushing -- as is,
trivial I/O examples such as
main = do
putStr What is your name?
ls - getLine
putStrLn (Hello ++ ls ++ !)
fail to behave as expected.
That depends on what you expect... :-) The
10 matches
Mail list logo
