Path: eternal-september.org!news.eternal-september.org!feeder2.eternal-september.org!i2pn.org!i2pn2.org!.POSTED!not-for-mail
From: fir <fir@grunge.pl>
Newsgroups: comp.lang.c
Subject: Re: else ladders practice
Date: Sun, 03 Nov 2024 01:53:16 +0100
Organization: i2pn2 (i2pn.org)
Message-ID: <6726C97C.4080807@grunge.pl>
References: <3deb64c5b0ee344acd9fbaea1002baf7302c1e8f@i2pn2.org> <vg0t3j$2ruor$1@dont-email.me> <78eabb4054783e30968ae5ffafd6b4ff2e5a5f17@i2pn2.org> <864j4pv76h.fsf@linuxsc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Info: i2pn2.org;
	logging-data="677000"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="+ydHcGjgSeBt3Wz3WTfKefUptpAWaXduqfw5xdfsuS0";
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:27.0) Gecko/20100101 Firefox/27.0 SeaMonkey/2.24
To: Tim Rentsch <tr.17687@z991.linuxsc.com>
X-Spam-Checker-Version: SpamAssassin 4.0.0
In-Reply-To: <864j4pv76h.fsf@linuxsc.com>

Tim Rentsch wrote:
> fir <fir@grunge.pl> writes:
>
>> Bart wrote:
>>
>>> ral clear patterns here:  you're testing the same variable 'n'
>>> against several mutually exclusive alternatives, which also happen
>>> to be consecutive values.
>>>
>>> C is short of ways to express this, if you want to keep those
>>> 'somethings' as inline code (otherwise arrays of function pointers
>>> or even label pointers could be use
>>
>> so in short this groupo seem to have no conclusion but is tolerant
>> foir various approaches as it seems
>>
>> imo the else latder is like most proper but i dont lkie it
>> optically, swich case i also dont like (use as far i i remember
>> never in my code, for years dont use even one)
>>
>> so i persnally would use bare ifs and maybe elses ocasionally
>> (and switch should be mended but its fully not clear how,
>
> I think you should have confidence in your own opinion.  All
> you're getting from other people is their opinion about what is
> easier to understand, or "clear", or "readable", etc.  As long as
> the code is logically correct you are free to choose either
> style, and it's perfectly okay to choose the one that you find
> more appealing.
>
> There is a case where using 'else' is necessary, when there is a
> catchall action for circumstances matching "none of the above".
> Alternatively a 'break' or 'continue' or 'goto' or 'return' may
> be used to bypass subsequent cases, but you get the idea.
>
> With the understanding that I am offering more than my own opinion,
> I can say that I might use any of the patterns mentioned, depending
> on circumstances.  I don't think any one approach is either always
> right or always wrong.
>
maybe, but some may heve some strong arguments (for use this and not 
that) i may overlook