|
The biggest difference between a program and a procedure is that a program is a procedure, but is also a separately compiled object and is loaded on demand. Whereas a procedure can be a separately compiled object, but may also be included in the same source member. Programs are called dynamically, and loaded into memory on demand. Procedures are called using the bound call interface, which loads the procedures about 100 times faster than a program call. Procedures are loaded when the initial program that uses them is called. -----Original Message----- From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com] On Behalf Of Buck Calabro Sent: Monday, November 18, 2002 9:56 AM To: rpg400-l@midrange.com Subject: RE: What's the difference? >To add to Buck's list I also like the ability >to NOT pass a parameter if it is not needed >-- options(*nopass). The called program can test %parms just like a subprocedure can, so I think this works for procs and progs. c *entry plist c parm inCount c if %parms < 1 c eval loopLimit = 1000 c else c eval loopLimit = inCount c endif --buck _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.