Re: if-then-no-else Programming

["G.B." <bauhaus@futureapps.invalid>]

On 19.04.16 04:24, Charles H. Sampson wrote:
> 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;

I think that "software engineering" here might mean web development
or media development; not the typical areas of engineering, AFAIK.
But while speculation, this really seems to about making sure that
variables have a value assigned, not so much about conditionals
per se.

If about guaranteed assignment, then languages have started
supporting the initialization problem in much better ways.
The above example reminds me of PHP/Python/Javascript, etc.
Swift, OTOH, a newly developed language, guarantees assignment
before use and rejects, as do some older language for constants,
this definition:

     func foo(condition: Bool) {
         var Variable : Int

         if condition {
             Variable = 1
         }
         bar(Variable)
NN:error:   ^ variable 'Variable' used before being initialized
     }


GNAT has a similar warning. Is there still a reason why,
in embedded system, assignment is considered costly, maybe,
and thus had better be done only as necessary, instead
of being enforced, using default values, or dummy values?
Or even constructor invocations?

Ada 2012 adds conditional expressions (in addition to the
old nested functions that need to return). So, if the value
that is to be assigned depends on Condition,

    Variable :=
     (if Condition
       then 1
       else 3);

is another way of making sure that Variable is initialized,
in *one* statement!

This expression is part of many languages, albeit using
different syntax. The list includes Python, Javascript, C, ...