RE: Module source naming schemes

Brad Stone wrote:

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

This is a good thread.  Here's my opinion.  I never liked Hungarian notation
- artificially adding the object type to it's name takes up space better
used for... the name.  I'd rather split them along source file lines instead
of fiddling with the name.

Here is one scheme I've used:
QRPGLESRC SOCKET holds all socket PI code:
  sockOpen, sockRead, etc.
QPROTOSRC SOCKET holds all socket PR code:
  sockOpen, sockRead, etc.
QSRVSRC SOCKET holds all binder source:
  STRPGMEXP PGMLVL(*CURRENT) SIGNATURE(' 1.00 11 Sep 00') 
    EXPORT SYMBOL(sockOpen)                               
    EXPORT SYMBOL(sockRead)                               
    etc...
  ENDPGMEXP                                               

Since all the members have the same name, maintenance and compilation are
trivial.  I have not found a simple way of answering the question "Where is
my socket read() function?"  I currently use PDM to scan QPROTOSRC (because
the function may not currently be public.)

If I were the only programmer, I would write a Code or SEU macro to create
and log every PR in order to build a library of functions.

Buck Calabro
Aptis; Albany, NY
"Nothing is so firmly believed as
 that which we least know" -- Michel Montaigne
Visit the Midrange archives at http://www.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
+---