Re: support for multithread-safe libraries

[Paul Eggert]

Bruno Haible <address@hidden> writes:

> "lock.h" has the big benefit that it describes what it is

The word "lock" is good, but (unfortunately) lots of things are
locked, and there are different forms of locks.  Files can be locked
with flock, for example.  "lock.h" could refer to any of these things.

> and resembles glibc's <bits/libc-lock.h>.

If the module is based on gcc/gthr.h but does only locks, how about
the name "gthr-lock"?