Debugging API for krb5

[Jeffrey Altman]

We agreed on this:

/* Status Message Functions */
#ifdef KRB5_STATUS_MESSAGES
krb5_error_code KRB5_CALLCONV krb5int_status_message
    (krb5_context, const char *, ...);

#define kstatus(ctx,str)  \
        krb5int_status_message(ctx,str)
#define kstatus1(ctx,str. p1) \
        krb5int_status_message(ctx,str. p1)
#define kstatus2(ctx,str. p1, p2)  \
        krb5int_status_message(ctx,str. p1, p2)
#define kstatus3(ctx,str. p1, p2, p3) \
        krb5int_status_message(ctx,str. p1, p2, p3)
#define kstatus4(ctx,str. p1, p2, p3, p4) \
        krb5int_status_message(ctx,str. p1, p2, p3, p4)
#define kstatus5(ctx,str. p1, p2, p3, p4, p5) \
        krb5int_status_message(ctx,str. p1, p2, p3, p4, p5)
#else
#define kstatus(ctx,str)
#define kstatus1(ctx,str. p1)
#define kstatus2(ctx,str. p1, p2)
#define kstatus3(ctx,str. p1, p2, p3)
#define kstatus4(ctx,str. p1, p2, p3, p4)
#define kstatus5(ctx,str. p1, p2, p3, p4, p5)
#endif


Sam Hartman wrote:

>OK.  I still believe you need to agree on the specific form of the
>debugging messages to be inserted into the code.  Alexis and I also
>seem to be uncomfortable with the use of macros for anything more than
>collecting file and line and function information.
>