× 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 Thu, 20 May 2004 15:34:55 +0200
 Joep Beckeringh <joep@xxxxxxxxxxxxxxxxxxx> wrote:
> Brad Stone wrote:
> >Ya, I've heard about this as well.  Is the suggestion
> then
> >to return pointers?  Does this also apply to passing
> >parameters that are large values, or just returning
> large
> >values?
> >
> >Brad
> 
> Return a pointer to what? Not automatic storage, of
> course. Most practical solution is to not use a return
> value, but an output parameter. Then the pointer is all
> that is passed; the caller maintains the storage. Not as
> nice to code, alas. So the choice is between nice coding,
> with return values, when performance is not that
> important and somewhat uglier coding when performance
> does matter.

I was thinking change the return value from 32767 varying
to a pointer, then return a pointer to a local var in the
app.  Tried it and worked, but for this it will be just as
easy to return it in a parameter...  


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.