e_os.h and e_os2.h are not really very optimal. There are many times
when e_os2.h should really be included from some exported header
files, but that means immediately that e_os.h needs to be included as
well. Since we've once declared that e_os.h shouldn't really be
exported, this becomes a bad thing.
Well, actually, this situation is not at all good. It's ridiculous to
have an exported header file be dependent on an unexported (although
we currently export e_os.h as well) one.
What we really need to do is to move some stuff from e_os.h to e_os2.h
and have e_os.h include e_os2.h. And really, a rename should be done
as well, or people will think that e_os2.h is for OS/2... :-)
Ideas?
--
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]
