| I've now written up a slightly more formal proposal for native
threads.
| (OK, it's only a tiny bit more formal...)
| I doubt I have explained everything clearly, please tell me which
| points are unclear. And of course please tell me what you like/don't
| like about it.
Great, thanks. I hope y
Done!
SImon
| -Original Message-
| From: Ashley Yakeley [mailto:[EMAIL PROTECTED]]
| Sent: 14 November 2002 02:25
| To: GHC List
| Subject: -Werror Request
|
| If it's not too much work, I'd like to request a "-Werror" option for
GHC
| that would turn warnings into errors. Sometimes warn
Great, thanks. I hope you'll keep it up to date so that by the time
the
discussion converges it can serve as a specification and rationale. We
can put it in CVS too... Simon will think of where!
Until then, I'll play the role of a "human CVS server".
Ultimately it'd be
worth integrating with
Hello!
I am trying to add a new primitive to ghc (5.04.1) ... I followed
the instructions in primops.txt.pp:
-- - or, for an out-of-line primop:
-- ghc/includes/PrimOps.h (just add the declaration)
-- ghc/rts/PrimOps.hc (define it here)
--
In local.glasgow-haskell-users, you wrote:
> Is there any way in GHC to reopen stdin if it has been closed?
You can call 'System.Posix.IO.dup stdin' and save this value.
However, I think you then need to explicitely read from this fd as
it is not possible to reset what GHC thinks stdin is currentl
> There's probably a really obvious answer to this, but I can't find it.
>
> Is there any way in GHC to reopen stdin if it has been closed?
There's no way to do this at present, except in GHCi where you can
revert CAFs to their unevaluated state.
> You may wonder why I'd want this. Well I'm wri
> I am trying to add a new primitive to ghc (5.04.1) ...
> I followed
> the instructions in primops.txt.pp:
>
> --- or, for an out-of-line primop:
> -- ghc/includes/PrimOps.h (just add the declaration)
> -- ghc/rts/PrimOps.hc (define it here)
> --
GHC's excellent warnings are very helpful. They would be somewhat
more so if it were possible to suppress a warning about a specific bit
of code. One possible syntax (to which I gave no commitment) would be
{-# WOFF "non-exhaustive pattern matches" #-}
{-# WON "non-exhaustive pattern mat
> You can call 'System.Posix.IO.dup stdin' and save this value.
> However, I think you then need to explicitely read from this fd as
> it is not possible to reset what GHC thinks stdin is currently to
> this new fd (I'll dig into this and maybe we'll get a
>setStdin :: Fd -> IO ()
> from this,
Simon Marlow writes:
> I've been thinking about duplicating/replacing Handles for a while.
> Here's a possible interface:
>
> -- |Returns a duplicate of the original handle, with its own buffer
> -- and file pointer. The original handle's buffer is flushed,
> including
> -- discarding any
10 matches
Mail list logo
