In message <[EMAIL PROTECTED]> on Fri, 27 Feb 2004 14:09:07 +0100 (MET), "Stephen Henson via RT" <[EMAIL PROTECTED]> said:
rt> The workaround we use is to #undef these first in the relevant header rt> file but as the OP reports this only works if you #include <windows.h> rt> (which includes wincrypt.h) first. Uhmm, I was under the impression that #undef'ing an undefined macro basically is a no-op and should not be a problem. Is that incorrect? Or perhaps that's just incorrect in the Microsoft world? :-) ----- Please consider sponsoring my work on free software. See http://www.free.lp.se/sponsoring.html for details. -- Richard Levitte \ Tunnlandsv�gen 52 \ [EMAIL PROTECTED] [EMAIL PROTECTED] \ S-168 36 BROMMA \ T: +46-708-26 53 44 \ SWEDEN \ Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED] Member of the OpenSSL development team: http://www.openssl.org/ 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]
