Hi Alain, > >I would recommend you always watch the warnings. Some C compilers > >downgrade fairly major problems to "Warnings". > > I'm not really familiar with handling void* pointers so I'm > not sure how alarming these should be.
The first warning seems to be about the callback function being cast to a function pointer with a slightly different type. (char* vs const char*). The second one could be a problem since CRYPO_thread_cleanup() is defined as a static function for WIN32. The functions in th-lock.c seem to be very close to those described in the O'Reilly Book. I was not aware that OpenSSL provided a reference version of these callbacks. > So this really isn't much of a problem for me, but I'm still curious > about the macros: > OPENSSL_THREAD_DEFINES > THREADS > OPENSSL_THREADS The latter seems to be used to select the thread safe version of a system call. > Is the note in http://www.openssl.org/docs/crypto/threads.html still > valid in 0.9.8a ? I don't know about this. The books I have refer to versions 0.9.4 and 0.9.6! Mark. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
