On Sat, May 24, 2008, Jeff Johnson wrote:

> Nothing wrong with this change, but likely needs to be done as
> a macro persistently at run-time so that the --usecrypto
> doesn't have to be explictly added to each invocation when multiple
> implementations are present.

Yes, the macro is still on my list. The question is just where the best
code location is to expand a "%_usecrypto" macro?

> And dlopen() eventually to Have it yer own way! AutoFu
> choice is restrictive: if not compiled in, well, that crypto
> implementation is unavailable. Period.

dlopen() is not such easy. You also have to dlsym() all
necessary symbols, etc.

                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com