|
Dan, Missed this part. I used this technique once and decided it was not the way to go. In this case I wanted to pass parameters who's type was unknown to the compiler. Operational descriptors are also not fully supported in RPG. Operational descriptors describe parameters being passed. I created a routine to create a pseudo-operational descriptor so that I could check in the receiving program to see if what was received matched what was expected. I decided it wasn't worth the extra work and that I would have to live with the possibility of type mismatches in this case. To correct this the compiler people could add a new option(*vartype), and full support for operational descriptors. This would be very powerful. To accomplish this, the compiler people need some operating system people to change something. From what I understand, they feel this change is not very likely to take place. Were they to do this you could create built in functions (%bifs) with the same capabilities as IBM's. David Morris >>> "Dan Bale" <dbale@genfast.com> 06/04/99 11:20AM >>> David, ...And why useCALLB to set up parameters used with CALLP or EVAL? +--- | 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.