|
Oh, I see. So I infer that it would be (would have been?) possible to
design QZRUCLSP to properly handle optionally-passed parameters by
careful placement of those parms presented to the procedure. But it
would likely not be possible to influence a program without such design
in such a way that the stars line up for that call.
Finally the documentation line makes sense: "The API does not support
calling procedures that have been defined using #pragma artopt"
So no defect at all. Thanks everyone. This is what I had missed.
"Barbara Morris" <bmorris@xxxxxxxxxx> wrote:
On 3/18/2011 9:38 AM, Dennis wrote:means
Ah, that sheds some light! Since we have no (apparent) means of
telling QZRUCLSP that certain parameters are optional but passed, it
seems unlikely that it would be capable of guessing the correct
optimizatingof passing same.
Probably a moot point, but is the "differently" part of your message
a trade/business/compiler secret?
It's more that I don't know all the details since it's mostly
transparent to the compilers. The compilers just tell the
way
translator that the called function has optional parameters.
I do know that for a "..." C function, the function would use the
va_list mechanism to access optional parameters. This requires that
the
optional parameters be contiguous in storage, so parameter 3 follows
parameter 2 in storage, at a fixed offset away. When there are no
optional parameters, the system can pass the parameters in whatever
makes the most sense. So the location of parameter 3 can't be
predicted
from the location of parameter 2.
_______________________________________________
This is the MI Programming on the AS400 / iSeries (MI400) mailing list
To post a message email: MI400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mi400
or email: MI400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mi400.
--
Sent from my Galaxy tablet phone with with K-9 Mail. Please excuse my
brevity.
_______________________________________________
This is the MI Programming on the AS400 / iSeries (MI400) mailing list
To post a message email: MI400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mi400
or email: MI400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mi400.
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.