Am Freitag, den 29.08.2014, 09:56 +0200 schrieb Jens Gustedt:
> All of this would explode in our face the day a user wants to use
> pthread_mutex_t and mtx_t in the same application. A use case could be
> that he uses one library that protects CS with pthread_mutex_t and
> another that uses mtx_t. Now suddenly we have code that sees two
> different types, with possibly subtle bugs due to aliasing.
> 
> So in conclusion, it is doable, but I don't like it at all.

To give it a positive turn, for the moment I'd prefer to roll this
back and have the two types pthread_mutex_t and pthread_cond_t violate
the namespace rules of libc for the moment. This is not perfect, but
also not a serious drawback.

This would have the advantage of being conservative on the pthread
side and not to delay the schedule.

Jens

-- 
:: INRIA Nancy Grand Est ::: AlGorille ::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536   ::
:: :::::::::::::::::::::: gsm France : +33 651400183   ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: http://icube-icps.unistra.fr/index.php/Jens_Gustedt ::