|
Douglas Handy wrote: > > I'd vote for this if it can handle my environment, but I'm not sure it will. >I > started a practice back on the S/34, where each physical file has a unique > 2-character prefix used in all field names for that file. This helped to >avoid > name collissions since we did not have qualified DS naming. Thus one file >might > have fields xxCUST and xxNAME while the next has yyCUST and yyNAME, etc. > > In order for EVALC to move corresponding fields, the subfield names must >match. > But mine never will, unless you can code something like PREFIX( '': 2 ) and >have > the compiler *drop* two characters from the fieldname without replacing them. Doug, even if the compiler doesn't add prefix-dropping(*), you could apply the same prefix to all your structures. PREFIX(Z:2) would give you ZCUST and ZNAME for both structures. Not as nice as CUST and NAME, I know. (*) Me, I think prefix-dropping is a good idea, though.
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.