develooper Front page | perl.perl5.porters | Postings from July 2013

Re: Using braces on 'if'; Was: Re: Asan help request

Thread Previous | Thread Next
From:
demerphq
Date:
July 31, 2013 11:20
Subject:
Re: Using braces on 'if'; Was: Re: Asan help request
Message ID:
CANgJU+X2EjF6+thodn26Pc31svQhF28jDiAqvAzNM3H9PzQ40g@mail.gmail.com
On 31 July 2013 09:26, H.Merijn Brand <h.m.brand@xs4all.nl> wrote:
> On Tue, 30 Jul 2013 21:29:49 -0700, Father Chrysostomos
> <sprout@cpan.org> wrote:
>
>> I would prefer that we not have too many rules.  Being able to format code free-style allows for more clarity when things can up vertically:
>>
>>     if      (CvROOT(cv))  slab = OpSLAB(CvROOT(cv));
>>     else if (CvSTART(cv)) slab = (OPSLAB *)CvSTART(cv);
>>
>> Also, I don’t find that the extra verbosity of braces really helps.  In Perl the fact that braces are enforced does not increase verbosity, because we have ‘and’ and ‘or’ for control flow.  Do that in C and you get void warnings galore.
>>
>> If you do not feel comfortable omitting the braces, then don’t omit them.  But does that have to apply to those of us who do feel comfortable omitting them?  I omit them all the time, and only once has that resulted in a mistake (which was caught very quickly).
>
> +Inf to that
>
> In code *I* am responsible for, I remove unneeded braces, as they just
> take away focus from the code I read. They just act as noise.

Both you and FC overlook that the statement suffers from the dangling
else problem and the braced form does not.

There is nothing subjective about this, it is a fact.

http://en.wikipedia.org/wiki/Dangling_else

cheers,
Yves




-- 
perl -Mre=debug -e "/just|another|perl|hacker/"

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About