|
Brad, I can make a few comments with respect to using QUALIFIED vs. PREFIX. 1) Qualified is more standard 2) Qualified helps prevent the possibility of collisions. For example, a subfield with field name Address prefixed with Cust would result in a field named CustAddress. It's possible you could try to create a standalone field named CustAddress. I realize this is no biggie, but... 3) Qualified hopefully opens the door to such operations as COBOL's Move Corresponding in which all fields of the same name within two structures are candidates for copy from the source structure to the target structure- that would be great. Gary Guthrie NEWS/400 Technical Editor +--- | 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.