RE: RE: Memory control

Hi Rory,

Hey, while you're tinkering with the dynamically allocated memory, try the
statically allocated stuff too.

I guess the big question is how to get a pointer to something.  My
understanding is that it's not so easy to simply create some bit pattern and
call it a pointer.

Peter Dow
Dow Software Services, Inc.
www.dowsoftware.com
909 793-9050 voice
909 793-4480 fax

> -----Original Message-----
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Hewitt, Rory
> As Walden points out, "if you get a pointer to a memory location, you
> can modify it". I actually use this technique in some of my software. In
> one (batch NEP) job, I create a user space in that job's QTEMP, retrieve
> the pointer to that user space (using QUSPTRUS) and put the retrieved
> pointer into a different 'control' user space in a separate library. Now
> a program in a separate job can get to the control user space (because
> it's in a normal non-QTEMP library), retrieve the pointer and thus get
> at the data in the userspace in the QTEMP of the other job. There's not
> even any MI - just plain ol' RPGLE...
>
> I haven't tried putting a pointer to dynamically allocated memory into a
> user space, but it would probably work... I'll tinker and see :-) Mind
> you, I wouldn't recommend it - it's a real pain to debug :-)

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.8/114 - Release Date: 9/28/2005