RE: Subprocedure Naming Conventions

This has been pounded into submission multiple times...

The best idea (IMO forget who originally suggested this but it wasn't me ... ) 
from the previous poundings was to use the Program(or service program) name to 
prefix the subproc.

so if you created service program SRVPGM1 all procs in the SRVPGM would be 
SRVPGM1_THISPROC or SRVPGM1_THATPROC

Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Andy Hautamaki
Sent: Wednesday, June 29, 2005 12:27 PM
To: RPG400-L@xxxxxxxxxxxx
Subject: Subprocedure Naming Conventions


I realize everyone has there own naming conventions or shop standards when 
naming subprocedures but I'm wondering as I create more subprocedures that 
are being 'exported' to other modules and these modules are being bound to 
programs and service programs if others on this list have some tips on 
'gotchas' when naming subprocedures.

I've been using the '...' on the D spec to get past the 14 character limit 
and trying to have meaningful subprocedure names but I have that feeling 
that one day I will start to have the same subprocedure name in different 
modules.............

Am I missing something basic here? Which won't be the first time..........:}

Thanks
Andy