RE: RPG Futures (was free form RPG reference)

Good point on columnar definitions of D specs.  I line up my definitions 
in CL this way
DCL  &APOS        *CHAR   1  /* Apostrophe */
DCL  &PARM1       *CHAR   2  /* */
DCL  &PARM2       *DEC    2  /* */
DCL  &DATA        *CHAR  30  /* Message data from RCVMSG */
DCL  &KEYVAR      *CHAR   4  /* Message key from RCVMSG */
DCL  &MSGID       *CHAR   7  /* Message id from RCVMSG */

The hilarious thing is that people who'll give up fixed format coding in 
RPG only at gunpoint quickly prompt and change my CL to free format with 
all sorts of space tied up for keywords.  Is this really that much more 
readable?  (I chopped off all that wasted space on the left they create. 
Helps the list to not see wrapping.)
DCL        VAR(&APOS) TYPE(*CHAR) LEN(1) /* + 
             Apostrophe                               */ 
DCL        VAR(&PARM1) TYPE(*CHAR) LEN(2) + 
             /*                                          +
             */ 
DCL        VAR(&PARM2) TYPE(*DEC) LEN(2) + 
             /*                                          +
             */ 
DCL        VAR(&DATA) TYPE(*CHAR) LEN(30) /* Message + 
             data from RCVMSG                 */ 
DCL        VAR(&KEYVAR) TYPE(*CHAR) LEN(4) /* Message + 
             key from RCVMSG                  */ 
DCL        VAR(&MSGID) TYPE(*CHAR) LEN(7) /* Message id + 
             from RCVMSG                   */ 

You don't suppose fixed format D specs inhibit data structure size 
changes?  Granted, the string size is much larger now, but I can remember 
in earlier versions of RPG you couldn't fit the size of the variables 
needed into the length columns.

Rob Berendt