|
Peter wrote: >What you need to do is convert the subroutine to a procedure, i.e. replace >the BEGSR/ENDSR with P-specs, add a prototype defintions (D-spec type "PR") >in the main part of the program and a matching procedure interface within >the procedure. These define the parameters passed to the procedure. Then you >can use it as you described, but without the percent sign: > >> C Eval BSDPuR = MoveMDYToDate(CMDPuR) > >Another advantage of converting to a procedure is that the procedure can >have local variables. > >For more details, they're all in the ILE RPG Reference manual. I'm pretty >sure they were available for V3R7, but not totally sure... V3R2/V3R6 actually. In other words, no one has any excuse not to use them. Some advantages: -- local variables -- compile-time type checking of parameters -- VALUE parameters -- CONST parameters -- passing expressions for VALUE and CONST parms -- better modularization of apps -- ability to call C runtime functions -- return values from procedures -- easier to share and reuse code Why would anyone NOT want to use procedures? Cheers! Hans 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.