From: Rich Salz <[EMAIL PROTECTED]>

rsalz> You can do it like ANSI says for errno.
rsalz> 
rsalz> #ifdef GOOD_LINKER
rsalz> extern ASN1_ITEM* ku_item;
rsalz> #else /* BAD_LINKER */
rsalz> #define ku_item asn1_item_lookup(ku_item_nid)
rsalz> extern ASN1_ITEM* asn1_item_lookup(int);
rsalz> #endf
rsalz> 
rsalz> Then developers get source compatibility.

Yup, I was thinking of that, but it might mean a certain complication
of some other macros.  Although, I haven't looked at it at that level
yet.

That errno thing, that's for thread safety, isn't it?  Or are there
other reasons behind?

-- 
Richard Levitte   \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken   \ S-168 35  BROMMA  \ T: +46-8-26 52 47
Redakteur@Stacken   \      SWEDEN       \ or +46-709-50 36 10
Procurator Odiosus Ex Infernis                -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, Celo Communications: http://www.celocom.com/

Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to