12 Jun
2004
12 Jun
'04
12:50 a.m.
Does anybody have any opinion on which threading system is superior?
I've been using glib for a lot of things, but for whatever reason I'm
hesitant about using it for threading if the only benefit it will
provide is consistency (I'm guessing it's just a wrapper for pthread
anyway).
[pb]
12 Jun
12 Jun
2:19 a.m.
Does anybody have any opinion on which threading system
is superior?
I've been using glib for a lot of things, but for whatever reason I'm
hesitant about using it for threading if the only benefit it will
provide is consistency (I'm guessing it's just a wrapper for pthread
anyway).
yes, its just a wrapper. there's nothing in the semantics of GThread
that isn't present in pthreads; conversely, pthreads does have a few
corners here and there that GThreads don't wrap because they don't
exist in some of the other thread systems that GThreads
supports. you're unlikely to need them. personally, i prefer to use
pthreads because its a fully specified standard that is independent of
any particular platform. otoh, there is a very similar argument for
GThread.
--p
2:58 a.m.
At Sat, 12 Jun 2004 00:10:17 -0400,
Paul Davis wrote:
One more point in favor of GThread I just figured out is config
testing for it. All you have to do is at a pkg-config check for
gthread-2.0 and your set. Having glanced through other programs,
checking for pthreads seems a bit more involved than I care to be
(read: not at all, I hate the fscking autotools). So, I think
I'll roll with GThread.
Thank you much for chiming in on this.
[pb]
Does anybody have any opinion on which threading
system is superior?
I've been using glib for a lot of things, but for whatever reason I'm
hesitant about using it for threading if the only benefit it will
provide is consistency (I'm guessing it's just a wrapper for pthread
anyway).
yes, its just a wrapper. there's nothing in the semantics of GThread
that isn't present in pthreads; conversely, pthreads does have a few
corners here and there that GThreads don't wrap because they don't
exist in some of the other thread systems that GThreads
supports. you're unlikely to need them. personally, i prefer to use
pthreads because its a fully specified standard that is independent of
any particular platform. otoh, there is a very similar argument for
GThread. 
3:17 a.m.
Pete Bessman <ninjadroid(a)gazuga.net> writes:
One more point in favor of GThread I just figured out
is config
testing for it. All you have to do is at a pkg-config check for
gthread-2.0 and your set. Having glanced through other programs,
checking for pthreads seems a bit more involved than I care to be
(read: not at all, I hate the fscking autotools). So, I think
I'll roll with GThread.
Not a very strong reason. Checking for pthreads is a little tricky,
but hardly rocket science. These checks (from JACK) work for quite a
few platforms, though I'm sure there are others one could add...
AC_CHECK_HEADER(/usr/include/nptl/pthread.h,
[CFLAGS="$CFLAGS -I/usr/include/nptl"])
AC_CHECK_FUNC(pthread_create, [],
AC_CHECK_LIB(pthread, pthread_create, [],
AC_MSG_ERROR([*** JACK requires POSIX threads support])))
There is also a conditional check for pthread_barrier_init().
--
joq
3 p.m.
At 12 Jun 2004 00:09:05 -0500,
Jack O'Quin wrote:
Pete Bessman <ninjadroid(a)gazuga.net> writes:
Touche. Since you did all the hard work for me, and pthreads isn't
OOPy like GThreads, I'll stick with pthreads :-)
One more point in favor of GThread I just figured
out is config
testing for it. All you have to do is at a pkg-config check for
gthread-2.0 and your set. Having glanced through other programs,
checking for pthreads seems a bit more involved than I care to be
(read: not at all, I hate the fscking autotools). So, I think
I'll roll with GThread.
Not a very strong reason. Checking for pthreads is a little tricky,
but hardly rocket science. These checks (from JACK) work for quite a
few platforms, though I'm sure there are others one could add...
AC_CHECK_HEADER(/usr/include/nptl/pthread.h,
[CFLAGS="$CFLAGS -I/usr/include/nptl"])
AC_CHECK_FUNC(pthread_create, [],
AC_CHECK_LIB(pthread, pthread_create, [],
AC_MSG_ERROR([*** JACK requires POSIX threads support]))) There is also a conditional check for
pthread_barrier_init().
Well, I don't even know wtf that is, so I think I'll be ok without it.
[pb]
5:24 p.m.
Another advantage if you're new to it as I am, is that there are some very
good books on pthreads. And you can look at the Ardour and Softwerk code. ; )
The O'Reilly book is old ( '96 ) but very clearly written and readable. Of
course because it's old you can probably find it at the library.
Iain
At 12 Jun 2004 00:09:05 -0500,
Jack O'Quin wrote:
Pete Bessman <ninjadroid(a)gazuga.net> writes:
Touche. Since you did all the hard work for me, and pthreads isn't
OOPy like GThreads, I'll stick with pthreads :-)
One more point in favor of GThread I just figured
out is config
testing for it. All you have to do is at a pkg-config check for
gthread-2.0 and your set. Having glanced through other programs,
checking for pthreads seems a bit more involved than I care to be
(read: not at all, I hate the fscking autotools). So, I think
I'll roll with GThread.
Not a very strong reason. Checking for pthreads is a little tricky,
but hardly rocket science. These checks (from JACK) work for quite a
few platforms, though I'm sure there are others one could add...
AC_CHECK_HEADER(/usr/include/nptl/pthread.h,
[CFLAGS="$CFLAGS -I/usr/include/nptl"])
AC_CHECK_FUNC(pthread_create, [],
AC_CHECK_LIB(pthread, pthread_create, [],
AC_MSG_ERROR([*** JACK requires POSIX threads support]))) There is also a conditional check for
pthread_barrier_init().
Well, I don't even know wtf that is, so I think I'll be ok without it.
[pb]
16 Jun
16 Jun
4:43 a.m.
On Sat, Jun 12, 2004 at 12:49:37AM -0400, Pete Bessman wrote:
One more point in favor of GThread I just figured out is config
testing for it. All you have to do is at a pkg-config check for
gthread-2.0 and your set. Having glanced through other programs,
checking for pthreads seems a bit more involved than I care to be
(read: not at all, I hate the fscking autotools). So, I think
I'll roll with GThread.
just wanted to say that galan using gthreads compiles fine under win32.
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language
7596
days inactive
7601
days old
linux-audio-dev@lists.linuxaudio.org
6 comments
5 participants
participants (5)
-
iainduncan＠telus.net -
Jack O'Quin -
Paul Davis -
Pete Bessman -
torbenh＠gmx.de