this is a good idea, just wrapping some platform specific load library code
in the plugin.

i have used the link strategy before and it does work very well on
windows/mac/linux, including headers and linking with the dll/framework/so .
the plugin code itself is very portable if u have the headers in the right
place and the right paths set up. the source for the plugin requires no
changes at all across platforms. there are slight differences in how it is
compiled, but no more than how the current makefiles for the vm differ for
each platform. i did all of this straight in c though, without slang.

however, if this is something that eventually would be distributed as part
of vm source files and such, then u run into trouble, as it requires the
headers for OpenSSL to be compiled obviously, and i am sure this is what tim
is referring to. if u can get those functions loaded dynamically instead of
linking u would be better off.

i tried to use ioLoadFunctionFrom to connect to an external library
initially and no dice. i was told that it was not really meant to load
functions from non squeak plugin dlls/so and such ( there are certain entry
points it needs to look for, mainly setting the interpreterProxy i believe
if i remember correctly).

anyways, just thought i would let u know since i have done this on all three
major platforms before and it is easy to maintain and port, but only if it
is completely separate from the vm.

jamie