2021-01-27 13:42:22 +01:00
|
|
|
This rule applies whenever an ``++IF++`` statement is followed by one or
|
2021-02-02 15:02:10 +01:00
|
|
|
|
2021-01-27 13:42:22 +01:00
|
|
|
more ``++ELSEIF++`` statements; the final ``++ELSEIF++`` should be followed by an ``++ELSE++`` statement.
|
2020-06-30 10:16:44 +02:00
|
|
|
|
2021-02-02 15:02:10 +01:00
|
|
|
|
2021-01-27 13:42:22 +01:00
|
|
|
The requirement for a final ``++ELSE++`` statement is defensive programming.
|
2021-02-02 15:02:10 +01:00
|
|
|
|
2021-01-27 13:42:22 +01:00
|
|
|
The ``++ELSE++`` statement should either take appropriate action or contain
|
2021-02-02 15:02:10 +01:00
|
|
|
|
2020-06-30 10:16:44 +02:00
|
|
|
a suitable comment as to why no action is taken. This is consistent with the
|
2021-02-02 15:02:10 +01:00
|
|
|
|
2021-01-27 13:42:22 +01:00
|
|
|
requirement to have a final ``++ELSE++`` clause in a ``++CASE++``
|
2021-02-02 15:02:10 +01:00
|
|
|
|
2020-06-30 10:16:44 +02:00
|
|
|
statement.
|
|
|
|
|
|
|
|
== Noncompliant Code Example
|
|
|
|
|
|
|
|
----
|
|
|
|
IF my_variable = 0 THEN
|
|
|
|
do_something;
|
|
|
|
ELSIF my_variable = 1 THEN
|
|
|
|
do_something_else;
|
|
|
|
END IF;
|
|
|
|
----
|
|
|
|
|
|
|
|
== Compliant Solution
|
|
|
|
|
|
|
|
----
|
|
|
|
IF my_variable = 0 THEN
|
|
|
|
do_something;
|
|
|
|
ELSIF my_variable = 1 THEN
|
|
|
|
do_something_else;
|
|
|
|
ELSE
|
|
|
|
-- Nothing has to be done.
|
|
|
|
NULL;
|
|
|
|
END IF;
|
|
|
|
----
|
|
|
|
|
|
|
|
include::../see.adoc[]
|