Re: Fixes for generic pthread_cond_*wait functions
Ulrich Drepper <[email protected]>
| Newsgroups | gmane.comp.lib.phil |
|---|---|
| Organization | Red Hat, Inc. |
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alexander Terekhov wrote:
> Again: unless you'll provide some {implementation -specific} means
> to "differentiate" (see above)... IMO, abort() is much better way
> to "show" that something went wrong with respect to re-locking the
> mutex here.
That's a completely bogus argument. Error values do not correspond
1-to-1 to possible errors. Look through the standard, error values can
have many different meanings for each interface and every implementation
is allowed to add more.
- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+boRm2ijCOnn/RHQRAkWqAJ0fGB6eaqGZnR7enF032j67xOG+NwCggFP1
3Q0H4WAP7kvlpftIfAMjRkI=
=2Crk
-----END PGP SIGNATURE-----