RE: power line (AS/400) article in computerworld

[dkimmel@xxxxxxxxxxx]

The C definition of a pointer is an offset from the beginning of the
storage assigned to the process where the pointer is used. Windows uses
the same definition.

You can't even pass a windows pointer from one process to another without
using operating system API's to map it to universal space.  

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

On Fri, Apr 11, 2008 at 12:55 PM, David Gibbs <david@xxxxxxxxxxxx> wrote:
> Steve Richter wrote:
> > you cant use a user space ( which contains pointers ) to store 
> > production data because in the event of disaster recovery the 
> > pointers in that space are invalidated. This falls under the heading 
> > of using the right tool for the job, etc.  It is an example where 
> > IBM software group could improve the system, obviate the need for 
> > multiple memory model, but choose not to.
>
> Steve:
>
> The idea is not to store POINTERS in a user space ... but to store 
> DATA in a user space and get a pointer to it.

why should there be a restriction on storing pointers? If you could create
your own object on the system ( another limitation of the system ), your
code would start with an object header that contains various pointers to
other data structures within the object. That type of a structure is
immediately useable in a program. Much simpler than the alternatives
available today.

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