Chris Vine writes:
> If you know that the gthread implementation is a pthreads one (ie the
> program is not running on Windows) there is absolutely no problem at all
> in using pthreads in the program directly,
Also, there is a quite nice pthreads implementation even for
Windows: http://sourcew
In my particular application I needed to be able to bind a thread to a specific
CPU. Last I checked, GThread didn't offer that sort of thing. I still went
with GThread (because I need to work on both *nix and Windows) but I ended-up
with some "going behind the back" code to have platform-speci
On Tue, 2007-07-17 at 09:53 -0400, Tristan Van Berkom wrote:
> On Tue, 2007-07-17 at 21:20 +0800, Gregory Hosler wrote:
> > Hi,
> >
> > I've got a gtk+ application that needs a few threads put in it, to open up
> > some
> > bottlenecks.
> >
> > My question is whether I should go pthreads, or gth
On Tue, 2007-07-17 at 21:20 +0800, Gregory Hosler wrote:
> Hi,
>
> I've got a gtk+ application that needs a few threads put in it, to open up
> some
> bottlenecks.
>
> My question is whether I should go pthreads, or gthreads.
>
> I've played a bit with pthreads, so I have some familiarity with
