RE: EXTPROC(*CL) and V6R1 -- RPG400-L

× 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.

While I don't recommend this approach, it isn't the end of the world
you make it out to be. You need to remember that you're passing by
reference, meaning it doesn't matter how big the DS is the only thing
passed in and out of the procedure is a 16 byte pointer.

Charles, Charles, Charles. I'm so surprised to hear you say that!

You're saying that, because only a 16-byte pointer is passed to my routine,
the actual size of the DS doesn't really matter? So that if the routine is
expecting, say, 100 bytes in but only 80 are provided by the caller, then
that's OK?

Or, if the called routine will pass back 100 bytes but the program has
allocated 80 for the effort -- then that's OK too?

These are not problems that can be circumvented by planning, design, and use
of features? Remember: "the problem with making anything foolproof is that
fools are so ingenious." This design opens the door to that ingenuity.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Even if you're on the right track, you'll get run over if you just sit
there."
-- Will Rogers

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.