but the question was referring to a gosub not a call, so the control should (big should) be contained within one program.
The only time I used the call @varible was when I had different subroutines based on the flavor of the system This way it I had one base program that could be modified that when recompiled would again work with Prime or D3. This was before UV. George > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Jacques G. > Sent: Friday, February 10, 2006 9:59 AM > To: [email protected] > Subject: RE: [U2] [UV] GOSUB variable-name? > > > > On a more serious note...If this is done correctly, > > I don't think it > > would be very difficult at all to support. > > If someone who didn't design the system has to > maintain it, it is difficult to find out which > programs are impacted by a change into one of the > subroutines. > > In normal calls, one can search for CALL ROUTINE.NAME > but when CALL @VARIABLE is used, it is difficult to > find out, short of creating a trace in the subroutine > that records SYSTEM(9001) over a period of time (even > then, its no garantee that the period of time will be > sufficient to identify all of the calling programs). > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
