libgcrypt 1.1.93 released
marcus.brinkmann at ruhr-uni-bochum.de
Thu Mar 11 23:52:02 CET 2004
At Wed, 10 Mar 2004 13:25:08 +0200,
Nikos Mavroyanopoulos wrote:
> > What about just requiring pthread?
> I don't know how applications that do not use the pthread would behave, as you
> said this may have side effects.
Maybe. Usually it is only a problem if you did not link some code
with pthread, and add a pthreaded plugin.
> > If all those other libraries are going to simply set these callbacks
> > to the pthread interface anyway, I don't see a very strong reason why
> > you shouldn't require pthread in gnutls, too.
> I think (correct me if i'm wrong) that those libraries
> do not use nor require pthreads, so they wouldn't bother to set any callback
> lock. I've rarely seen libraries that use threads, so it wouldn't do any harm.
> In most cases the callback will be used by the multithreaded application that
> uses those libraries.
This is exactly the worrying case. After all, the application might
not know about the need to set callbacks. But let's discuss this in
the other thread I started.
More information about the Gcrypt-devel