krb5_mcc_{s,g}et_flags() behavior

[Vipin Rathor]

hi all,
While going over the code of krb5 1.5.4, I came across this (which is
quite interesting).
In the functions, krb5_mcc_{s,g}et_flags, we are doing not setting or
getting anything but doing this:
>From lib/krb5/ccache/cc_memory.c:
krb5_error_code KRB5_CALLCONV
krb5_mcc_set_flags(krb5_context context, krb5_ccache id, krb5_flags flags)
{
    return KRB5_OK;
}

krb5_error_code KRB5_CALLCONV
krb5_mcc_get_flags(krb5_context context, krb5_ccache id, krb5_flags *flags)
{
    *flags = 0;
    return KRB5_OK;
}

But for krb5_fcc_{s,g}et_flags functions, we are doing the job nicely.
Why such behavior?

-- 
-Rathor