Re: Large Return values (was Re: Variable Length Field Question) -- RPG400-L

Subject: Re: Large Return values (was Re: Variable Length Field Question)
From: Joep Beckeringh <joep@xxxxxxxxxxxxxxxxxxx>
Date: Thu, 20 May 2004 15:34:55 +0200
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

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.

Joep Beckeringh

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Large Return values (was Re: Variable Length Field Question) , Brad Stone

This mailing list archive is Copyright 1997-2025 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.