[16703] in Kerberos_V5_Development
Re: Coding practices proposals
daemon@ATHENA.MIT.EDU (Tom Yu)
Fri Mar 18 13:38:00 2011
To: Sam Hartman <hartmans@mit.edu>
From: Tom Yu <tlyu@mit.edu>
Date: Fri, 18 Mar 2011 13:37:49 -0400
In-Reply-To: <tslei64wg7j.fsf@mit.edu> (Sam Hartman's message of "Fri,
18 Mar 2011 12:23:12 -0400")
Message-ID: <ldv8vwc72j6.fsf@cathode-dark-space.mit.edu>
MIME-Version: 1.0
Cc: "krbdev@mit.edu" <krbdev@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
Sam Hartman <hartmans@MIT.EDU> writes:
> OK, I find that there are a number of situations where inner scopes make
> code easier to understand.
>
> If you want to push for smaller functions, that's fine, but it seems
> like the best way to do that is to actually have recommendations about
> smaller functions being good, and citing using inner scopes as one sign
> that possibly you need a helper function.
We do already have guidelines for function length and nesting depth.
I was really hoping to avoid making guidelines for the maximum length
of an inner scope block, but maybe it would be a good idea to make
such guidelines.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
