[16706] in Kerberos_V5_Development

home help back first fref pref prev next nref lref last post

Re: Coding practices proposals

daemon@ATHENA.MIT.EDU (Will Fiveash)
Fri Mar 18 16:40:43 2011

Date: Fri, 18 Mar 2011 15:40:36 -0500
From: Will Fiveash <will.fiveash@oracle.com>
To: ghudson@mit.edu
Message-ID: <20110318204036.GA7975@sun.com>
Mail-Followup-To: ghudson@mit.edu, krbdev@mit.edu
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <201103172133.p2HLX28E020953@outgoing.mit.edu>
Cc: krbdev@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu

On Thu, Mar 17, 2011 at 05:33:02PM -0400, Greg Hudson wrote:
> I'd like to amend the coding practices in the following ways, if they
> aren't objectionable.

While we're on the subject, I'd like to see some guidelines on public
interfaces.  For example I'm currently wishing that the krb5_keyblock
definition in krb5.h was handled like krb5_context which is defined in
krb5.h as a pointer to incomplete struct (struct _krb5_context).  The
actual define for struct _krb5_context is in k5-int.h.  Access to parts
of krb5_keyblock should be provided via accessor functions.

-- 
Will Fiveash
Oracle
http://opensolaris.org/os/project/kerberos/
Sent using mutt, a sweet, text based e-mail app <http://www.mutt.org/>
_______________________________________________
krbdev mailing list             krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev

home help back first fref pref prev next nref lref last post