Re: libgcrypt brain dead?
* Henrique de Moraes Holschuh:
> 2. Must be thread-safe, and fully reentrant both at the function and at
> the _library_ level;
This does not include the async-signal-safe property, right? I'm also
not sure if the function needs to be reentrant within the same thread
(depending on what it does, of course).
> 4. Must not change any global attributes of the process or of any other
> libraries it uses;
Strictly speaking, this precludes creating child processes, which is
rather drastic. 8-(