no I don't mean linelength, more no of lines. In a function of several 100s of lines you want to return asap. and you don't want a method of 100s of lines
On Fri, Apr 11, 2014 at 2:44 PM, Alex Hitchins <a...@alexhitchins.com> wrote: > Daan, > > Are you referring to keeping line lengths up to 80 characters? Sorry - tired > eyes. > > My thoughts were more that in a function there should only be one "return" > statement rather than many, all nested in layers of if/else statements. > > > Alex Hitchins | 07788 423 969 | 01892 523 587 > --------------------------------------------- > > -----Original Message----- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: 11 April 2014 18:30 > To: dev > Subject: Re: Coding Standards Questions > > H Alex, > > I agree with you that would be nicer if your function fits in a screen. > Another coding convention we should adhere to. As it is I think it not so > much 'not a major concern' as too much to ask for. > Feel free to refactor and submit patches;) > > Daan > > On Fri, Apr 11, 2014 at 9:54 AM, Alex Hitchins <a...@alexhitchins.com> > wrote: >> All, >> >> >> >> As I've been looking through the code, I've seen a fair number of >> places where return statements are called within if statements and the >> like. I've always found that having one place to return is easier to >> debug and follow the code flow. >> >> >> >> Are there any guidelines on this? Or is it not a major concern? >> >> >> >> Thanks, >> >> >> >> Alex >> >> >> >> >> >> >> >> Alex Hitchins >> >> ------------------------------ >> >> E: a...@alexhitchins.com >> >> W: alexhitchins.com >> >> M: 07788 423 969 >> >> T: 01892 523 587 >> >> >> > > > > -- > Daan > -- Daan
