[1873] in Kerberos_V5_Development
Re: krb5-libs/66: add API versioning before next release
daemon@ATHENA.MIT.EDU (Theodore Y. Ts'o)
Wed Oct 23 15:56:52 1996
Date: Wed, 23 Oct 1996 15:56:27 -0400
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Ezra Peisach <epeisach@MIT.EDU>
Cc: "Barry Jaspan" <bjaspan@MIT.EDU>, krbdev@MIT.EDU, krb5-bugs@MIT.EDU
In-Reply-To: Ezra Peisach's message of Wed, 23 Oct 1996 15:08:23 EDT,
<9610231908.AA06440@kangaroo.mit.edu>
Date: Wed, 23 Oct 1996 15:08:23 EDT
From: Ezra Peisach <epeisach@MIT.EDU>
I like the ideas that you mentioned.
So do I; we should just go ahead and do it.
We have a number of "functions" that are handled by dispatch tables in
krb5.hin (i.e. krb5_encrypt, krb5_cc_*, krb5_rc_*) - should these
be proper functions as well - or will a dispatch table be sufficient
forever?
I'd very much like to make the current macros which call the dispatch
tables be proper functions; this will allow us to move a lot of
interfaces which *should* be private into k5-int.h. It's not an
absolute requirement for the 1.0 release, and it'll be harder to do than
the API versioning, but it would be nice to do if we can get to it.
- Ted
