Re: What part of an RPG program is re-used?

[Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>]

The only reason would be to pass the pointer in lieu of the qualified 
name to avoid re-resolving the object.  The pointer would essentially be 
opaque but would allow the system to more quickly execute the lookup.  I 
don't know that it would actually provide any benefit; my guess is that 
like program resolution the system only resolves when necessary but I 
don't know for sure.

Joe

> Not sure what you'd do with a pointer to a user index even if you could
> get one?  Write your own index traversal code?  (If it's not obvious --
> a user index is an *index*, like you'd have in a database file.  It's
> not a simple flat contiguous piece of data.)
>
> On 7/5/2011 1:01 PM, Joe Pluta wrote:
> > This seems like the best approach.  I don't know if I can lock the user
> > space into memory, but if it gets used enough it should be in memory
> > anyway.  And the user space wins over the user index because I can
> > retrieve the pointer.  There doesn't seem to be a corresponding QUSPTRUS
> > API for a user index.