Finally, the source code IS the only reliable source of documentation (assuming you can trust your compiler, OS, and hardware to do "the right thing"). It isn't the most CONVENIENT, which is why we desire other forms.
the implementation details of the 250-odd API entry points in libssl.so would tell me very little about how to properly USE those APIs, and in fact, designing an application around my interpretation of the library developers intent would likely lead me down some rabbit holes I'd rather not explore.
This is my idea of how open source documentation should be organized and written.
http://www.postgresql.org/docs/current/static/index.html ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
