Changed the spec for mutex::unlock() to say that it is illegal for a thread to
unlock a dlib::mutex it doesn't own. This is technically a non-backwards compatible change to the API but it has always been implemented in a way that didn't allow this kind of double unlock() on non-Windows platforms. Additionally, the recent change to the dlib::mutex implementation on windows also no longer allows this kind of double unlock.
Showing
Please
register
or
sign in
to comment