I've implemented ERR_set_mark() and ERR_pop_to_mark(), which can be used for similar functionality. I'll look into ERR_disable() and ERR_enable() as well, but that requires quite a lot more work.
If the implemented functions are enough for you for now, I'll resolve this ticket. [EMAIL PROTECTED] - Mon May 26 09:16:48 2003]: > Hi, > I would like to implement some kind of error locking function: > > SYSerr(x,x); > ERR_disable(); //We don't want anymore error feedback from this point > //call to functions that can potentialy generate some more errors > ERR_enable(); //Re-enable error feedback > > In this exemple the last error will be the one generated by > "SYSerr(x,x);". > > I tried to implement a custom error handling function, > int_thread_get_item equivalent that would return NULL, if the > thread error handling was locked, but any call to > ERR_clear_error destroyed the "SYSerr(x,x);" error. > > The custom error handling doesn't seem to be really supported (ERR_FNS > is opaque..., etc), altough the bases are there, could it be > possible to either fully support custom error handling, or to add > the ERR_enable/ERR_disable. > > Thanks, > Frédéric Giudicelli > http://www.newpki.org > -- Richard Levitte [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
