Re: CL code formatting and programming etiquette

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Good point - and the settings might not all be available in earlier 
versions of WDSC/RDi/RDP.

In RDP I get to the settings by going to the Window menu, then 
Preferences. I type "CL" where it says to type, then I see what I want 
under "Remote Systems" and parsers therein.

1. Automatic syntax checking (Y/N) - dft = N
2. Automatic uppercasing (Y/N) - dft = N
3. Automatic indenting (Y/N - 1-20 blanks) - dft = Y, 3 blanks
4. Automatic formatting (Y/N) - dft = Y
   a. Label position - dft = 2
   b. Command position - dft = 14
   c. Continued line indent - dft = 13
   d. Label above command (Y/N) - dft = N
   e. One parameter per line (Y/N) - dft = N

The defaults look a lot like SEU, except for the indentation. I use 
uppercasing, indenting (2 blanks), formatting (2, 3, & 13, label above 
and one parameter per line)

Here's a DCL under default settings -

             DCL        VAR(&PGMMSGQ) TYPE(*CHAR) LEN(10) VALUE('*')

Here's a DCLunder my settings -

  DCL        VAR(&PGMMSGQ) +
               TYPE(*CHAR) +
               LEN(10) +
               VALUE('*')

There are also user-defined tab settings you can use - maybe those could 
help with the pretty-column setups some like, I don't know.

HTH
Vern

On 5/29/2012 1:14 PM, rob@xxxxxxxxx wrote:
> Maybe for those who are rather new to WDSC (aka RDP) we should put in
> there how you change the CL parser to format 'prettier'.
>
>
> Rob Berendt