Re: else ladders practice

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