×
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.
On 3/10/2011 11:41 AM, Charles Wilt wrote:
My C's a little rusty...but I'm thinking of the way C supports
unpassed parms via a default value..of course that appears to require
callers to be recomplied when a new optional parm is added...which we
don't have in RPG.
I'm guessing you're confusing C with something else...?
In C, you simply put ... on the prototype, and it means "other
parameters may follow". It makes no attempt to specify what the
parameters are, how big they are, or how many. Instead, logic has to be
written inside the C function you're calling. That logic decides how to
interpret any remaining parameters, and that logic also decides when
it's reached the end of the list. (there isn't even a %parms equivalent
to get the count)
If you try to read too many parameters, it's just like RPG..
"unpredictable results" occur.
You do NOT have to recompile the caller when you add more optional
parameters in C. And there are no "default" values.
So I think you must be thinking of something else.
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
