I wrote:
> On the other hand using '==' instead of pthread_equal() may in theory
> fail anyway (even if pthread_t is an integer), so maybe malloc is safer
> anyway. For the same reason, the only actually POSIX-conforming
> interface would be to also allow a configurable thread_equal() function
> which would take the passed thread IDs for argument.
I mean, if you made a function to set an actual pthread_t (or whatever
thread type their implementation uses) and a pthread_equal() wrapper.
I.e. something like this:
typedef int (*set_thread_fn)(void *outbuf, size_t bufsize);
typedef int (*thread_equal_fn)(const void *t1, const void *t2);
void CRYPTO_set_idcmp_callback(
set_thread_fn s, thread_equal_fn cmp, size_t thread_t_size);
--
Regards,
Hallvard
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [EMAIL PROTECTED]
