Is there interest in making the library "const correct"? I know this
first requires ANSI C use. Would the core team accept patches that
all the niggly little const's added?
For those who don't know, this means putting "const" in the right
places in your functions. For example, all of the "dup" functions
XXX* XXX_dup(XXX* in);
should really be
XXX* XXX_dup(const XXX* in);
and the i2d and d2i functions similarly. It's a real pain to this, because
once you start at a high-level function (e.g., X509_dup) it ripples
through all the other code and you do a lot of edit/compile/repeat fixes.
/r$
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
