×
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.
Hi Jeff,
IOW (correct me if I'm wrong), one cannot define a parm in an RPG program as
type N and be able to call that RPG program from both CL and RPG. If you
want to call it from both CL and RPG, define the parm as 1A.
No, that's not true. First of all, there's no difference between 1N and
1A -- they both exhibit the same problem.
Second, if you code EXTPROC(*CL) it will work from both RPG and CL.
The only problem with EXTPROC(*CL) is that it changes the way the
procedure handles the return value under the cover. So if you are
modifying an existing RPG routine, you'll have to recompile all callers
for them to work.
If you're writing a new routine, this isn't a problem. It's only when
adding EXTPROC(*CL) to a routine that previous didn't have EXTPROC(*CL).
But, once added, it will work properly from both RPG and CL.
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
