> We still need a way to keep track of what they are, and the existing
> mechanism is basically the only way. We can either implement it with
> a wrapper around pthread conditions, or exted pthread conditions. The
> latter seems better.
Or, as I suggested, all the users (all four of them) of thi
Roland McGrath <[EMAIL PROTECTED]> writes:
> > We need pthread implementations (as GNU extensions) for them.
>
> I am not convinced we really need it. The caller can just signal several
> conditions. If this were used in more than two places, it could be done
> with a wrapper around lists of co
> We need pthread implementations (as GNU extensions) for them.
I am not convinced we really need it. The caller can just signal several
conditions. If this were used in more than two places, it could be done
with a wrapper around lists of conds. But it's not, so the code could as
easily be cha
On Sun, Dec 01, 2002 at 04:11:05AM +0100, Vicente Hernando Ara wrote:
> When changing cthread code to pthread i have found this problem:
>
> In file hurd/libpipe/pipe.c appear the following functions:
>
> condition_implies and condition_unimplies
>
> What are the best way to change them to pthre
