|
Dave wrote: >When I pass a string to CEEDOD it correctly describes the parameter. >When I pass a character data structure it says "Missing operational >descriptor" . Of course, I can copy the data structure into a string >and pass it as a parameter (which works), but I am curious, how do >others handle data structures with options(*varsize) with opdesc in the >prototype? Originally, operational descriptors were supposed to be much more functional than they ended up as. One intention was to be able to describe all of the subfields of a structure. This was not to be, but hope remained. As a result, it was decided at the time not to do anything for data structures in the expectation that the full design would someday be realised. But the other way of looking at RPG data structures is that they are simply character fields. We've been fantasizing about improved DS support ourselves, but that can't change the way existing DS's work. The bottom line is that even if no other improvements to operational descriptors happen, we should probably at least consider DS's as character fields in the OD. Cheers! Hans Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-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.