×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I always wondered why there is a "name" on a procedure interface. I have
never seen an example where *n was not sufficient as the name. I don't
often code a procedure interface without an immediately preceding dcl-proc
(with the name on it) so I haven't seen everything. I see an example in
the ILE RPG Reference using a procedure interface for a program without a
prototype but I never do that (because I prototype everything). Still, *N
for the name.
Can anyone show an example of where a non-*N name is absolutely necessary
(and meaningful)?
I half-way thought it might be to support several procedure interfaces,
each with a different name and different parms, sort of like function
overloading, but no, only one is allowed and it MUST have the same name as
the procedure that contains it, so what's the point of the name?
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.
midrange.com
