Re: Sub procedure end specification

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

David

Your best friend is WDSC or RDi - whichever - it has a wizard for 
creating procedures - it puts in all the names in the right places - 
worth it's weight in gold.

Now another option is to create a template in an RPGLE source member for 
procedures, then copy/paste from THAT. Or have a template in WDSC.

You really want all the auto-documentation you can get

HTH
Vern

David FOXWELL wrote:
> I used to suggest to my colleagues that they systematically put the name of a sub procedure in the end specification instead of :
>
> D                                 E
>
> Our prototypes our declared in the source of the module. When searching for the name of a sub procedure in the source, you get a hit in a comment line before the prototype, the PR declaration, the comment before the sub procedure, the B declaration, the PI declaration, the call to the subprocedure and maybe other comments, but : never in the end of the subprocedure even though the subprocedure might be pages and pages of code.
>
> Well, this still hasn't caught on. So I've decided, if you can't beat'em, join'em and I no longer put the name of the subprocedure in the end spec. It makes for quicker compiling, as I always copy another sub procedure and forget to change the name at the end spec.
>
> My reasoning that the end spec name isn't necessary : if I can't see the start spec on the same page (ok 2 pages for greenscreeners), then my sub procedure is probably too dang long!!!!
>
>
>