|
True, it's not absolutely unique in that regard. However, I think it's (indds) real benefit is to isolate these display indicators so that indicator (*INxx) usage doesn't affect display file behavior. How many times has a programmer added a little subroutine that uses (what they believe to be) a disposable indicator, only to realize that that indicator is being used by a DSPF in some obscure way. Eric DeLong Sally Beauty Company MIS-Sr. Programmer/Analyst 940-898-7863 or ext. 1863 -----Original Message----- From: David.X.Kahn@gsk.com [mailto:David.X.Kahn@gsk.com] Sent: Thursday, November 15, 2001 9:58 AM To: midrange-l@midrange.com Subject: RE: Display files not compatible with new RPG syntax Joel wrote: > I don't think it's that big a deal. You have to define the data > structure and then, as you add an indicator, you have to name the > offset in the data structure. I really like having indicators with > names like "quit" or "sfldisplay". Being able to have names for the > three subfile indicators you can't do without means that I don't have > to look at the cheat sheet that tells which is which. I see. However, you don't need to use INDARA to do this. Simply use a data structure for your indicators and base it on the address of *IN. Dave...
As an Amazon Associate we earn from qualifying purchases.
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.