krb5.h and KRB5_PRIVATE

Ken Raeburn raeburn at MIT.EDU
Wed Jan 10 01:22:09 EST 2007

On Jan 9, 2007, at 14:52, Sam Hartman wrote:
> The only reason we didn't move private things out of krb5.h is
> lazyness on our part; if you have the time then by all means move
> things into k5-int.h.  Consider changing the names especially if it is
> something where future versions may change the prototype or where you
> choose to drop a KRB5_CALLCONV.

I've got a tree where I've moved all the private stuff over into k5- 
int.h.  (Brute force -- copied it all to the end, no function  
renaming, no organizing by functionality.)  The makefile rules for  
checking calling-convention consistency between the Windows export  
lists and the headers needed tweaking to look at krb5.h + k5-int.h;  
not too tough.  I've done some builds and cleaned up a few places  
where we got new warnings about missing function declarations, but  
that process isn't done yet.


More information about the krbdev mailing list