On Sun, Dec 31, 2000 at 02:04:23AM +0100, Richard Levitte - VMS Whacker wrote:
> 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.
Why? Actually a number of exported header files *do* include e_os2.h
(without including e_os.h, which is not exported).
> ([...] we currently export e_os.h as well)
Not really. It's true that in the source code directory, we have a
link incluce/openssl/eos.h, but this is just because this is the
easiest way to make it accessible to all source code files, including
local header files that may not be in the same directory as the source
code files that use them (this is the tricky part). However, e_os.h
is not installed by "make install".
--
Bodo Möller <[EMAIL PROTECTED]>
PGP http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/moeller/0x36d2c658.html
* TU Darmstadt, Theoretische Informatik, Alexanderstr. 10, D-64283 Darmstadt
* Tel. +49-6151-16-6628, Fax +49-6151-16-6036
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
