On 03 February 2006 08:34, Bulat Ziganshin wrote:
moreover - we can implement locking as special converter type,
that can be applied to any mutable object - stream, collection,
counter. that allows to simplify implementations and add locking
only to those Streams where we really need it. like
Simon Marlow wrote:
-- | Takes an output stream and an input stream, and pipes all the
-- data from the former into the latter.
streamConnect :: (OutputStream o, InputStream i) = o - i - IO ()
That's the wrong way around, of course :-) It pipes everything from the
input stream to the output
Cyril Schmidt wrote:
I added this to the FAQ list; please feel free to elaborate and correct.
Linking to Visual Studio-generated code would be much easier if GHC were
able
to use Visual C++ as backend, instead of gcc (even Visual Haskell at the
moment
relies on gcc for C compilation).
I
I think that the C backend is heavily dependent on various GCC pragmas
but it should be relatively easy to do assembly backend that produces
MASM code.
Cheers,
Krasimir
2006/2/3, Geoffrey Alan Washburn [EMAIL PROTECTED]:
Cyril Schmidt wrote:
I added this to the FAQ list; please feel free
Simon Marlow wrote:
So - do you need Latin-1, or could you use UTF-8?
I'm not amused to change the encoding of many haskell source files
(particular of those that are not mine).
These files can then no longer be compiled by earlier ghcs (though I
don't understand, how ghc-6.4.1 recognises
Krasimir Angelov wrote:
I think that the C backend is heavily dependent on various GCC pragmas
but it should be relatively easy to do assembly backend that produces
MASM code.
That's something I'd like to do (or see somebody else do), if only to
make debugging Haskell DLLs a bit easier;
