Re: Long Procedure Names

Scott,

My preference is to put the colon after the variable names and not in front.
IMHO the colon gets in the way of reading the variable.  I'd rather code it
as:

CUGLS001_getPeriodStatusDesc( CurrentCompany :
                                                       periodName :
                                                       periodStatusDesc :
                                                       someOtherParm );

Paul

-- 
Paul Morgan
Senior Programmer Analyst - Retail
J. Jill Group
100 Birch Pond Drive, PO Box 2009
Tilton, NH 03276-2009
Phone: (603) 266-2117
Fax:   (603) 266-2333

"Scott Klement" wrote

> The other strategy that I've found useful is something that I learned from
> reading Carsten Flensburg's code.  I didn't like it at first, but after
> awhile it grew on me! :)  The idea is, if the subprocedure call doesn't
> fit on one line, put each parameter on a separate line.  Put the colon
> that separates the parameters at the start of the line.
>
> For example:
>
>          CUGLS001_getPeriodStatusDesc( currentCompany
>                                      : periodName
>                                      : periodStatusDesc
>                                      : someOtherParm    );
>