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




Richter has a point.

It might be cool to have a "materialize pointer" instruction that would
take a pointer as a parameter and return the fully qualified name of the
object and the offset into that object. You could store that in a user
space and then later "resolve" that abstraction into a real pointer. That
pointer might point at anything in "user space" and it wouldn't matter if
the target had been saved and restored.

Oh wait. You can do that on IBM i. Never mind.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Douglas Handy
Sent: Friday, April 11, 2008 4:22 PM
To: Midrange Systems Technical Discussion
Subject: Re: power line (AS/400) article in computerworld

Steve,

Why
use offsets that have to be converted to pointers in your code when
you can use and store a pointer instead?


By your own reasoning, because then they can be saved and restored --
isn't that your whole gripe here?

In pgm B, having to use offsets to compute pointers when the user space is
first opened doesn't exactly seem like it should degrade performance to
unacceptable levels.

Tell me, do you create .NET programs which save pointers into objects and
expect to be able to save those, restore to disaster recovery machine, and
use the pointers?

I just don't understand what your gripe is here.





Any concern you have about
authority in the pointer exist today because pointers can be stored in
spaces and used by other jobs.

-Steve
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.