if-then-no-else Programming

[csampson@inetworld.net (Charles H. Sampson)]

It's hard to believe that it's been over six years since I wrote a line
of code for profit. If what my son tells me, there's been what I
consider a major change in software engineering during that time.

He says that there's a move to ban the use of the else-statement. The
preferred approach is to execute the else-part first, then change the
effect if the if-condition is satisfied. For example:

   Variable := 3;
   if <condtion> then
      Variable := 1;
   end if;

In addition to some other goodness attributes, this is supposed to be
clearer than the if-then-else form.

Is he right? (He's not really a coder. His experience is in wire-frame
animation but he's being forced into coding by the job market.) If he's
not right, have any of you even heard of an area of the software
"profession" where this position is held?

Charlie
-- 
Nobody in this country got rich on his own.  You built a factory--good.
But you moved your goods on roads we all paid for.  You hired workers we
all paid to educate. So keep a big hunk of the money from your factory.
But take a hunk and pay it forward.  Elizabeth Warren (paraphrased)