openssl/crypto/dso
Geoff Thorpe ebbaebf784 This case in the "dso_unload" handlers should not be reported as an error -
if a DSO_load(NULL,...) operation fails, it will have to call DSO_free() on
the DSO structure it created and that will filter through to this "unload"
call.

If the stack size is "< 1", then the library never actually loaded. To keep
things clean higher up, I'll treat this as a vacuous case without an error.
It makes the error stack easier to follow real world cases, and the error
this ignores was only useful for catching bugs in internal code, not
mismatched calls from applications (which should be handled in the generic
DSO layer).
2000-04-25 08:37:12 +00:00
..
.cvsignore Ignore lib and Makefile.save. 2000-04-14 23:37:44 +00:00
dso_dl.c This case in the "dso_unload" handlers should not be reported as an error - 2000-04-25 08:37:12 +00:00
dso_dlfcn.c This case in the "dso_unload" handlers should not be reported as an error - 2000-04-25 08:37:12 +00:00
dso_err.c This change facilitates name translation for shared libraries. The 2000-04-19 21:45:17 +00:00
dso_lib.c This change facilitates name translation for shared libraries. The 2000-04-19 21:45:17 +00:00
dso_null.c This change facilitates name translation for shared libraries. The 2000-04-19 21:45:17 +00:00
dso_openssl.c This is a set of startup code for the DSO support, it's not yet linked into 2000-04-04 21:57:11 +00:00
dso_win32.c This case in the "dso_unload" handlers should not be reported as an error - 2000-04-25 08:37:12 +00:00
dso.h This change facilitates name translation for shared libraries. The 2000-04-19 21:45:17 +00:00
Makefile.ssl "make update" 2000-04-09 12:52:40 +00:00
README This is a set of startup code for the DSO support, it's not yet linked into 2000-04-04 21:57:11 +00:00

TODO
----

Get a fix on how the paths should be handled. For now, flags == 0
and this is currently just passing strings directly onto the
underlying system calls and letting them do what they want with
the paths. However, it may be desirable to implement flags that
control the way the loading is performed (or attempted), and I
invisage that DSO_ctrl() will be used to control this.

NOTES
-----

I've checked out HPUX (well, version 11 at least) and shl_t is
a pointer type so it's safe to use in the way it has been in
dso_dl.c. On the other hand, HPUX11 support dlfcn too and
according to their man page, prefer developers to move to that.
I'll leave Richard's changes there as I guess dso_dl is needed
for HPUX10.20.

[G-T]