From: Zach B. <xa...@xa...> - 2011-04-05 19:23:23
|
Sam Steingold <sd...@gn...> writes: > I am afraid not. CLISP always runs all code with full safety, there are > no optimizations for specific types. Thanks for the info. > If you are concerned with performance, I suggest interfacing to > <openssl/sha.h> (using ffi or modules) - you will get a trusted > implementation as a bonus. I have two concerns. The first is performance; I'd like to be able to validate the PGP signatures of files that are several megabytes in size, and I'd like it to take seconds, not minutes. The second is a kind of platform independence, where I don't have to worry about having the appropriate libraries, headers, or external compiler tools available. The system doesn't always have gcc, or OpenSSL, or make, or other tools, especially on Windows. I think in this case I will see if I can just live with whatever speed I can get with plain CL. Thanks, Zach |