×
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.
Nathan Andelin wrote:
Barbara eventually explained that this was an unavoidable
consequence of the code the compiler generates to handle varying
length return values, from which I concluded that such procedures
were potentially a bad practice.
Is this only with "large" return values? What about procedures that
return say a 50 byte description [trimmed]?
desc = codeDesc(code);
The problem is proportional to the size of the return value. Calling a
procedure that returns 50 bytes should not be a problem unless you call
it a zillion times in the same procedure.
The problem isn't particularly related to varying-length return values.
There is some additional automatic storage required for a call to a
procedure returning a value (probably not integer or float return
values, though, unless they are arrays).
Varying-length return values are an issue because it seems like they
should only have to return the actual returned length, but actually they
have to return the prototype-defined length.
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
