Comments on: if cascade

By: Apotomo Cookbook » Blog Archive » Using Cells View Inheritance to clean up your views

Mon, 12 Apr 2010 18:00:35 +0000

[...] start getting really ugly when there are more conditions to respect and end up in a medieval if-cascade. It’s geting even worse when those deciders are copied and spread across multiple [...]

By: Guildenstern

Guildenstern — Tue, 08 Apr 2008 13:36:43 +0000

I found today something like this:

int retval;
retval = foo1();
if (retval == SUCCESS)
{
   retval = foo2();
  if (retval == SUCCESS)
  {
     retval = foo3();
(...)
 }
}

up to foo8()
but at least with different else clauses

By: Fabian

Fabian — Thu, 27 Mar 2008 09:55:52 +0000

in the same code i found:

        //some code here
        myPs.execute();
        if (myPs!= null)
            myPs.close();
        //some code here

lovely

By: Fabian

Fabian — Thu, 20 Mar 2008 12:16:30 +0000

Its a standard left to right short circuit boolean operations. I am not aware of a language not doing so

By: Guildenstern

Guildenstern — Thu, 20 Mar 2008 11:54:27 +0000

no proposal but an annotation:

is the execution order of these functions relevant? If yes I wouldn’t like your proposal Fabian, because non-expert programmers might no know in which order the if statement is processed. Since I don’t JAVA I have no clue. My C++ compiler would resolve this from left to right but is that really specified?

By: NiKo

NiKo — Thu, 20 Mar 2008 10:28:55 +0000

OOPS, it’s java here, I missed it :p

But I guess the patter should apply anyway