Re: design issue and /copy statements

If that procedure is called by a program that uses the service program, 
you'll also need the prototype in the calling program.  So not only will 
the service program need the prototype, but also the calling program.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 





Scott Mildenberger <scottmildenberger@xxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
07/21/2003 09:01 AM
Please respond to Midrange Systems Technical Discussion
 
        To:     Midrange Systems Technical Discussion 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        Re: design issue and /copy statements


Are you talking about the /copy to bring in the prototypes? 
Because these procedures really should be in service program(s).
 I have one /copy per service program to bring in the
prototypes. 

Scott Mildenberber

--- Booth Martin <Booth@xxxxxxxxxxxx> wrote:
> 
>  Here is a design issue I'd love to read comments on.
> 
> Lets say, for discussion, that there were three procedures,
> totally
> unrelated, but that all three are used in many many programs. 
> For example:
> 
> 1)Look up customer name and address info
> 2)check quantity on hand of an item
> 3)validate a credit card number
> 
> When I write a program and retrieve these with a /copy, should
> I have one
> /copy or three /copy statements?
> 
> 
> (I am trying to learn how this stuff works, so if there's a
> stupid mistake
> in what i said please look past it.)



__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.