RE: Module source naming schemes

For module source, I call them F.xxxx (F=Function?  I don't remember)
For prototype source I call them P.xxxx (p = Prototype)
For binder language, same as the module (F.xxxx) but in QSRVSRC with the
P.xxxx

This lets me easily subset all modules/service programs.  

As for subprocedure names, I start them all with # (Ya ya, don't start on
the multilanguage thing).  I do this so I know where the calls are in my
programs.  Sort of like me using $ to start every subroutine.  Hey, IBM uses
% for BIFs, and @ were already take for pointers, so what else?

After the # I name it whatever I feel like.  So if I have F.DATE which
contains date functions, I may have:

#ValidDate
#DayofWeek
#NameofDay
#NameofMonth
#AddWorkDur (Add working days duration, my favorite <bg>)

Brad

> -----Original Message-----
> From: Jim Langston [mailto:jimlangston@conexfreight.com]
> Sent: Monday, January 08, 2001 5:11 PM
> To: RPG400-L@midrange.com
> Subject: Module source naming schemes
> 
> 
> I'm starting to build module source files, which I compile then
> create a service program with.  Each module source file will have
> a prototype file.  
> 
> What type of a naming scheme should I have?
> 
> I have some functions that would serve one application called Cartage,
> so I'm thinking along the lines of CARTAGEMOD and CARTAGEPR for those.
> Or should I go with MODCARTAGE and PRCARTAGE ?
> 
> And then I have some general utilities, such as my StampToHHMM and
> StampToCYMD routines, which take date/time stamps as input and return
> hours and minutes, or CCCCYYMMDD. Should I make a separate module for
> these and call it, what, MODDATTIM or DATTIMMOD ?
> 
> Then I have one called RtvNetF which will Retrieve a user's list of
> waiting network files one at a time ('F' for first call, 'N' for next
> call, 'C' to close and set on LR).  What would I call this 
> one?  MODSYSTEM
> or SYSTEMMOD ?
> 
> And then I want to stick this whole thing in one service 
> program, which
> I would call, what, ICSSERVICE ?  
> 
> What naming schemes has everyone else settled on?  So far there are no
> modules on the system at all, nor are there any service 
> programs, so whatever
> naming schemes I start with we will most likely go with.
> 
> Any suggestions appreciated.
> 
> Regards,
> 
> Jim Langston
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to 
> RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: 
> david@midrange.com
> +---
> 
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---