|
John wrote: >Great job! Thanks! >I hope the next version includes qualified procedure names, and qualified >field names. When the number of procedures in your system starts numbering >in the hundreds, then thousands, keeping a unique namespace across the >entire system becomes more than just a minor inconvenience. Simple qualified subfield names are in V5R1. That is, code keyword QUALIFIED on a data structure definition, and the subfields are referred to as "DSNAME.SUBF". "Simple" means just that, with no whitespace allowed between the two names and the dot. A related enhancement that you should get to know very well as you learn V5R1 is keyword LIKEDS. A data structure or procedure parameter defined with LIKEDS inherits all the subfields of the other data structure. So you can define data structure A as qualified with subfield X and data structure B as LIKEDS(A) with no subfields, and you can refer to subfields A.X and B.X. The advantages of LIKEDS used with procedure parameters should be obvious. I agree that some sort of packaging mechanism for modules would be a good thing to help manage name conflicts. Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | 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.