Posted by Bob A on September 02, 2011 at 08:08:36:
1) expand the compiler warnings/errors to show the full 32 characters of the Subroutine name
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.
2) expand the information saved in the compile so that you'd see the extension and the source library, and whether it's text or CED (94/7):
ABCDEFGH.IBS,RDA
-BCDEFGH
and not just
ABCDEFGH
-BCDEFGH
3) a "depth level" on the compile (in case the IF structures get "squashed":
<<001>> IF A EQ B THEN
<<002>> IF C EQ D THEN
<<003>> SELECT CASE
<<004>> CASE 1
<<005>>
<<004>> CASE 2
<<005>>
<<004>> CASE ELSE
<<005>>
<<003>> ENDSELECT
<<002>> ELSE
<<003>> IF D EQ F THEN
<<004>> IF Q EQ R THEN
<<005>>
<<004>> ELSE
<<005>>
<<004>> ENDIF
<<003>> ENDIF
<<002>> ENDIF
<<001>> ENDIF
IBM's RPG compilers had this for 34 years since the fixed format of RPG precluded indenting (until RPG-free in about 2000), there was even an option to include an indent character sequence of 2 characters.. the code would be TRIML'ed and the appropriate number of characters would be inserted per level (e.g. with "|>" as the indent characters:
|> IF A EQ B THEN
|>|> IF C EQ D THEN
|>|>|> SELECT CASE
|>|>|>|> CASE 1
|>|>|>|>|>
|>|>|>|> CASE 2
|>|>|>|>|>
|>|>|>|> CASE ELSE
|>|>|>|>|>
|>|>|> ENDSELECT
|>|> ELSE
|>|>|> IF D EQ F THEN
|>|>|>|> IF Q EQ R THEN
|>|>|>|>|>
|>|>|>|> ELSE
|>|>|>|>|>
|>|>|>|> ENDIF
|>|>|> ENDIF
|>|> ENDIF
|> ENDIF