Qt 4.4 QtConcurrent and libthread_xu
Aggelos Economopoulos
aoiko at cc.ece.ntua.gr
Wed May 7 16:26:37 PDT 2008
On Thursday 08 May 2008, Matthew Dillon wrote:
> Ultimately it comes down to what does the standard intend?
[...]
> So I am willing to commit the change, even if the standard doesn't allow
> NULL.
Well, SUSv3 says
"The pthread_mutex_lock(), pthread_mutex_trylock(), and pthread_mutex_unlock()
functions may fail if:
[EINVAL]
The value specified by mutex does not refer to an initialized mutex object."
So it definitely allows NULL and seems to encourage extra mtx->magic checks.
Aggelos
More information about the Bugs
mailing list