|
Date: 7/17/97 7:40 PM RE: Re: Additional RPGLE Enhancement Requests <SNIP> >As I said, this is just some random bit of brainstorming, so I don't >know all of the ramifications yet. But here is an example: > > D DataStruct DS > D Combined > D Field1 OVERLAY(Combined:1) > D Field2 OVERLAY(Combined:*NEXT) > D Field3 OVERLAY(Combined:*NEXT) > <SNIP> > >So, in this example, if FIELD1, FIELD2, and FIELD3 are each 10 byte >long fields, subfield COMBINED is implicitly defined as 30A. If the >definition of any subfield changes, the definition of COMBINED would >also change on recompile with no source change. >This shouldn't be too difficult for us to implement since we already >have to deal with computing the length of data structures like this. > >Cheers! Hans Hans Now if we could just get the definitions of those variables, (Maybe Invoice Number, Customer Number, Order Number, etc.) from our Field Reference file via the H-Spec REF(FIELDREF) keyword......... Our app's would really reflect/change automatically with the changes to our data base. P.S. Hans as you know, if we have a externally defined D/S, We cannot use any of those fields in any other D/S right? (a real pain) Can you explain why you(plural, ie yous guys) can't allow us to have a variable in more than one D/S? I mean we can have the variable in multiple storage locations now in an RPG program right? Like the same name from 2 data base files, a couple of more from different formats on a display file, and a couple of more in the printer file formats. Why can't we have a couple of more storage locations in different Data Structures? I would agree we couldn't have the same one twice in the Same D/S(like you can't have the same within one DSPF format) But come on, stretch...... John Carr John Carr * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the Midrange System Mailing List! To submit a new message, * * send your mail to "MIDRANGE-L@midrange.com". To unsubscribe from * * this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe MIDRANGE-L' in the body of your message. Questions * * should be directed to the list owner / operator: david@midrange.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
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.