> I guess I'm trying to look at this from a "guarantee-of-parameter",
> "operation", "guarantee of output integrity" contract-based
> programming view.
It might make more sense to do this with C++ classes built on top of the C
API. If you had a common base class with void*,size_t, and then defined
all the appropriate subclasses, the calls to openssl would be inlined and
close to zero runtime cost.
> (Among other things, this could allow blobs of data
> to flow freely into and out of the FIPS core, given structure magic
> numbers and such.)
How so?
/r$
--
SOA Appliances
Application Integration Middleware
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
