Tagging conditional statements like IF, DO, SELECT

Statements like IF - ELSE - ENDIF, SELECT, LOOPs should have tag (or Id) assigned to the beginning and end (and if required in between).

Example:

/Free

IF#1: IF (cond1)

{ Set-of-statements;}

IF#1-1: IF (inner-condition 1)

{ Set-of-statements;}

IF#1-2: IF (inner-condition 2)

{ Set-of-statements;}

IF#1-2: ENDIF

IF#1-1: ENDIF

{ Set-of-statements;}

IF#1: ELSE

{ Set-of-statements;}

IF#1-3: IF (inner-condition 3)

{ Set-of-statements;}

IF#1-3: ENDIF

IF#Cond4: IF (inner-condition 4)

{ Set-of-statements;}

IF#Cond4: ENDIF

IF#PrtIsY: IF (inner-condition 5)

{ Set-of-statements;}

IF#PrtIsY: ENDIF

IF#1: ENDIF

/End-Free

The Tag will make the analysis work much easier - either manual or by means of an analysis tool. It helps identify the end of such blocks and track scope of variables inside etc.

I know that the compiler output (spool file) could generate indentation (probably with a pipe | symbol) but yet we need this.

In fact, Tagging should be made mandatory for such conditional statements.

Tag name should be allowed a minimum of 10 characters and its prefix should be a reserved (fixed) one - TAG, TG#, T#, IF#, DO# etc. (any or all of these could be allowed) and the rest could be anything meaningful & logical.

Compiler too can issue error/warning messages if the TAGs are out of order, if a TAG misses its pair, if duplicate tag names coded etc.