Re: else ladders practice

Anton Shepelev wrote:

fir:
>

somethins i got such pies of code like
>
if(n==1) {/*something/}
if(n==2) {/*something/}
if(n==3) {/*something/}
if(n==4) {/*something/}
if(n==5) {/*something/}
>
technically i would need to add elses

>
Why?
>

becouse its more strict expressed with else, with else
compiler is informed to drop all teh elese if its found
without else it is strictly liek it should test all teh ifs each time..
though in practice it  would be liek that if compiler only compiles line by line in separation, if it has a view on whole procedure it is clear that those branchhes exclude itself so teh assembly generated should not generate such tests but put soem goto itself

but the question is if to do that o teh code has really
chance to be slower without else (except some very
prmitive compilers) ?? ot adding else makes liek code
shorter.. so im not literally sure which is better

>
I am all for code literalism, and want it to emphasize the
most natural method of execution.  Therefore, I usually
append `return' or `goto' to each then-block in an tabular
if-sequence as above.  I believe the perormance will depend
on the compiler.
>