Re: mixture of multi-threading libraries
- From: Markus Elfring <Markus.Elfring@xxxxxx>
- Date: Wed, 05 Dec 2007 17:23:35 +0100
Instead of dealing with all the complexity of Pthread,
they may just rely on Pth (the most portable?).
I do not understand your view that the other library might be easier to use.
Which features are you missing for convenience?
It is usual that it takes some learning time to get used to multi-threaded
software development.
So I was evaluating the difficulty of being compliant with both levels
of threads at the same time and independantly.
Where does it really matter in your own API design?
Do you need any additional thread objects that will be concurrently running in
the context of a preemptive thread from the operating system?
Regards,
Markus
.
- Follow-Ups:
- Re: mixture of multi-threading libraries
- From: Laurent Deniau
- Re: mixture of multi-threading libraries
- References:
- mixing system and user threads
- From: Laurent Deniau
- Re: mixing system and user threads
- From: Markus Elfring
- Re: mixing system and user threads
- From: Laurent Deniau
- Re: mixture of multi-threading libraries
- From: Markus Elfring
- Re: mixture of multi-threading libraries
- From: Laurent Deniau
- Re: mixture of multi-threading libraries
- From: Markus Elfring
- Re: mixture of multi-threading libraries
- From: Laurent Deniau
- mixing system and user threads
- Prev by Date: Re: mixture of multi-threading libraries
- Next by Date: Re: mixture of multi-threading libraries
- Previous by thread: Re: mixture of multi-threading libraries
- Next by thread: Re: mixture of multi-threading libraries
- Index(es):