Re: Dealing with very large blocks of character data -- RPG400-L

× 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.

Subject: Re: Dealing with very large blocks of character data
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Wed, 30 Nov 2011 17:57:21 -0600
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the IBM i / System i <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>

On 11/30/2011 5:53 PM, David Gibbs wrote:

Well, a user space *IS* persisted, as it's a real object on disk.
But if you don't need it to be persistent, what's the difference
between a using a user space and just allocating the memory? End
result: You get a pointer to memory.

Before Bruce V jumps in ... I do recall that there are some memory boundary alignment aspects to user spaces that can come in handy. I don't recall the details though.

david

As an Amazon Associate we earn from qualifying purchases.

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.