Re: Module source naming schemes

Jim,

From what I've seen on this list is that procedures seen to have the verb/object
syntax.  i.e.: cvtDate, fmtDate, etc. with the prototype /COPY members something
like either cvtDate_pr or cvtDate_h.

If a programmer has a date issue, they may ask "Are there any date related 
service
programs?"  There next question would be, "What functions are available?", 
followed
by "How do I call this?"  So my first inclination would be to have the service
program start with "date".

One could even go so far as having all modules relating to date service 
programs in
it's own source file (datesrc) which may make restriction and distribution a bit
easier.

Since you are just at the planning stage anything goes.  Let us know on what you
settle on.

P.S. avoid using application mnemonics.  The service program for a vendor does 
not
belong exclusively to AP.

+---
| 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
+---