[2243] in Kerberos_V5_Development
Problems with the current com_err routines...
daemon@ATHENA.MIT.EDU (tytso@MIT.EDU)
Wed Feb 19 13:37:21 1997
Date: Wed, 19 Feb 1997 18:34:39 GMT
To: probe@lehman.com
Cc: krbdev@MIT.EDU
From: tytso@MIT.EDU
Hi Richard,
While you did a good job at the current com_err revamp, there
are a couple of problems with it. The main issue is that the new
xxx_err.c file is incompatible with older com_err libraries. On the
Windows side, this is inevitable; however, on the Unix side, we should
be able to avoid this altogether.
What do we need to do this? First of all, the xxx_err.c
*shouldn't* call add_error_table(). The initialize_foo_error_table()
should do what it did before, by manipulating _et_list. The krb5
library on the Unix side *shouldn't* depend on remove_error_table(),
since that doesn't exist on the older com_err libraries.
What I'd suggest is that we remove krb5_finish_ets(). Using
#ifdef's, make krb5_init_ets() and initialize_foo_error_table() be
no-ops under windows. In win_glue.c, use add_error_table() and
remove_error_table() directly.
This should allow Unix krb5 library to continue to work without
requiring any changes in the com_err library, while allowing the Windows
side to use the new dynamic registration and de-registration of the
com_err library.
Comments?
- Ted
