RE: Module source naming schemes

Aaron,

It isn't hard to modify the binder source at all.  Just make a copy of the
*CURRENT section, change it to *PRV and then edit the *CURRENT to include
the additional exports and your done.  As far as cleaning up the old ones,
we don't worry about it but you could at some point rebind all the programs
and then all programs would be using the *CURRENT signature so you could get
rid of all the *PRV ones.

Scott Mildenberger


> -----Original Message-----
> From: Bartell, Aaron L. (TC) [mailto:ALBartell@taylorcorp.com]
> Sent: Wednesday, January 10, 2001 7:19 AM
> To: 'RPG400-L@midrange.com'
> Subject: RE: Module source naming schemes
> 
> I am wondering.  Has anyone had problems with creating 
> multiple PGMEXP's
> within a binder source?  I am looking at it from the direction of
> continually adding SP's to a module and constantly having to 
> change the
> binder source.  If the PGMEXP's get to great in numbers is it 
> hectic trying
> to maintain?  Is there a utility out there to tell you if a 
> *PRV version of
> the PGMEXP is no longer in use so you could wax it and make 
> the source more
> maintainable?
> 
> How do other languages like C/C++, and Java handle this stuff 
> since they
> seem to be more on the basis of OO programming?
> Example below:
> 
> STRPGMEXP PGMLVL(*CURRENT)
>      EXPORT SYMBOL(RNF_OPEN)
>      EXPORT SYMBOL(RNF_READ)
>      EXPORT SYMBOL(RNF_READP)
>      EXPORT SYMBOL(RNF_CLOSE)
> ENDPGMEXP
> STRPGMEXP PGMLVL(*PRV)
>      EXPORT SYMBOL(RNF_OPEN)
>      EXPORT SYMBOL(RNF_READ)
>      EXPORT SYMBOL(RNF_CLOSE)
> ENDPGMEXP
> STRPGMEXP PGMLVL(*PRV)
>      EXPORT SYMBOL(RNF_OPEN)
>      EXPORT SYMBOL(RNF_READ)
> ENDPGMEXP
> STRPGMEXP PGMLVL(*PRV)
>      EXPORT SYMBOL(RNF_OPEN)
> ENDPGMEXP
> 
> 
> Aaron Bartell
> pgmr
+---
| 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
+---