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 firstname.lastname@example.org.
On 3/18/2011 9:38 AM, Dennis wrote:
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 means
of 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 optimizating
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 way
makes the most sense. So the location of parameter 3 can't be predicted
from the location of parameter 2.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2021 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.