× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Design question re: SrvPgm Modules & Procedures
  • From: pcunnane@xxxxxxxxxxxxxx
  • Date: Wed, 16 Feb 2000 16:45:18 -0500

     I don't think it matters much.  Will ProcedureA or ProcedureB be 
     needed in any routines other than Scramble and Unscramble?  Assuming 
     no, I would be tempted to put all the routines into a single module.
     
     One rule for module division is functional breakdown; if functions are 
     tightly interrelated, I would probably keep them in a single module.
     
     If you put ProcedureA and ProcedureB in a different module from 
     Scramble and Unscramble, you'll have to export them.  If you do this, 
     make sure you use binder source when creating the service program.
     
     (Of course, it would never cross your mind to create a service program 
     without binder source, now would it? :)
     
     ____________
     Paul Cunnane
     Mattel Interactive


______________________________ Reply Separator _________________________________
Subject: Design question re: SrvPgm Modules & Procedures
Author:  "Paul Jackson" <pauljackson@worldnet.att.net> at InterNet
Date:    2000-02-15 9:39 pm


Hello,
     
I will soon be writing a set of procedures to do Scrambling/Descrambling of 
data. This will be available by two procedures Scramble & Unscramble which 
will be able to be embedded within Eval statements.
     
Both Scramble & Unscramble will be calling Procedure A twice and Procedure B 
once to do their necessary processing.
     
I plan to have all of these procedures in the same service program, let's 
say srvpgm=SCRAMSRV
     
So within SCRAMSRV I will have the following procedures:
     
Scramble -- available outside srvpgm 
Unscramble -- available outside srvpgm 
ProcA
ProcB
     
My question is: Should I have these procedures in separate source members 
and compile as separate modules or should I throw everything into one source 
member?
     
Advantages/Disadvantages of either method?
     
I am fairly new to ILE and so could do with a few pointers here.
     
Thanks in advance for any advice.
     
-Paul Jackson 
+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.