On Tue, Feb 01, 2005 at 03:16:44PM -0800, Peter Simons wrote:
> Hi,
>
> I have the following problem: I use an external library
> through the foreign function interface which gives me
> _several_ sockets and expects me to call it again when any
> of those sockets becomes readable or writable.
>
>
Simon Marlow writes:
> This was due to a bug in GHC introduced a few days ago
> and fixed yesterday. Please try again.
I have tried again moments ago: same problem.
Peter
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http:
Hi,
I have the following problem: I use an external library
through the foreign function interface which gives me
_several_ sockets and expects me to call it again when any
of those sockets becomes readable or writable.
Since I know that the Haskell run-time system has all the
required functional
On 01 February 2005 12:48, Ketil Malde wrote:
> "Simon Marlow" <[EMAIL PROTECTED]> writes:
>
>> There are some problems with the existing approach. It doesn't cope
>> well with instances: instances might refer to types/classes not below
>> the current module in the hierarchy. Also you might imp
On 01 February 2005 11:31, [EMAIL PROTECTED] wrote:
> On Tue, Feb 01, 2005 at 11:02:45AM -, Simon Marlow wrote:
>> I'm making some changes to the way Haddock creates links, and I'd
>> like to solicit comments on possible alternatives.
>>
>> The existing approach is for each non-locally-define
On Tue, Feb 01, 2005 at 03:19:11PM -, Simon Marlow wrote:
> On 01 February 2005 11:31, [EMAIL PROTECTED] wrote:
> > On Tue, Feb 01, 2005 at 11:02:45AM -, Simon Marlow wrote:
> >> So the new approach is to try to build up a global table of the
> >> "best" destinations to link to for each ent
"Simon Marlow" <[EMAIL PROTECTED]> writes:
> Hmm, I'm not sure that would be practical. Lots of entities are
> exported from more than one place, especially Prelude entities. You'd
> have a table on almost every single page listing Bool, Maybe, Int, etc.
But surely in many cases, it would be po
"Simon Marlow" <[EMAIL PROTECTED]> writes:
> There are some problems with the existing approach. It doesn't cope
> well with instances: instances might refer to types/classes not below
> the current module in the hierarchy. Also you might import an entity
> from a "hidden" module, but actually w
On 01 February 2005 10:33, Ben Horsfall wrote:
> On 01 Feb 2005 10:32:14 +0100, Peter Simons <[EMAIL PROTECTED]> wrote:
>> I can't build the library's Haddock documentation anymore:
>> the process fails claiming that Control/Arrow-raw.hs would
>> be missing. I've had this problem for a while now.
On Tue, Feb 01, 2005 at 11:02:45AM -, Simon Marlow wrote:
> I'm making some changes to the way Haddock creates links, and I'd like
> to solicit comments on possible alternatives.
>
> The existing approach is for each non-locally-defined identifier in the
> current module, we hyperlink to a mod
I'm making some changes to the way Haddock creates links, and I'd like
to solicit comments on possible alternatives.
The existing approach is for each non-locally-defined identifier in the
current module, we hyperlink to a module that it was imported from, and
that (a) actually documents the ident
On 01 Feb 2005 10:32:14 +0100, Peter Simons <[EMAIL PROTECTED]> wrote:
> I can't build the library's Haddock documentation anymore:
> the process fails claiming that Control/Arrow-raw.hs would
> be missing. I've had this problem for a while now. Does
> anybody else see this?
Yes, I do too. No solu
I can't build the library's Haddock documentation anymore:
the process fails claiming that Control/Arrow-raw.hs would
be missing. I've had this problem for a while now. Does
anybody else see this?
Peter
___
Glasgow-haskell-users mailing list
Glasgow-has
13 matches
Mail list logo
