> From: parlezuml@yahoogroups.com
> [mailto:parlezuml@yahoogroups.com] On Behalf Of Bayley, Alistair
>
> > From: parlezuml@yahoogroups.com
> > [mailto:parlezuml@yahoogroups.com] On Behalf Of jasongorman_uk
> > Sent: 22 February 2009 18:00
> >
> > Sorry to labour the point, but if I made the following statement:
> >
> > "Any method containing more than 5,000 lines of executable code and
> > that will potentially need to be maintained by a human being is too
> > long and needs to be broken down into smaller methods."
> >
> > During a court case for professional software development
> > malpractice, who here would argue against that?
> >
> > Jason Gorman
>
>
> What's your evidence? Earlier I think you suggested 5-10 lines as your
> preferred upper limit.
>
> See the 2nd-last paragraph on this page (a summary of Code Complete,
> which I do not have):
> http://c2.com/cgi/wiki?LongFunctions
> Looks like 50-200 lines per method is optimal.


I found some evidence (OK, someone else did). From this blog entry:

http://dubroy.com/blog/2009/03/09/method-length-are-short-methods-actual
ly-worse/

we get a link to this study:

http://www.cistel.com/free_expertise/publications/Cistel-2002-01.pdf

(which I've only skimmed over, so cannot properly summarise.)

Alistair
*****************************************************************
Confidentiality Note: The information contained in this message,
and any attachments, may contain confidential and/or privileged
material. It is intended solely for the person(s) or entity to
which it is addressed. Any review, retransmission, dissemination,
or taking of any action in reliance upon this information by
persons or entities other than the intended recipient(s) is
prohibited. If you received this in error, please contact the
sender and delete the material from any computer.
*****************************************************************