«

How does on "point" a pointer at a specific memory address? I have a
program where I've malloc'd some memory and need to move around and
make changes. I know I can move a pointer in the malloc'd storage by
incrementing a pointer. However, in this malloc'd storage, I have
stored addresses of other locations and would like to "jump" from one
memory location to another based on what I find in certain memory
ranges. Don't worry, I've taken care of word aligning, etc. etc.

So to recap:
1. I have malloc'd storage
2. I have written blocks of data into this storage (I know it's there
because I can traverse the entire storage and output the information
alas, by incrementing the pointer)
3. I need to jump from run location to another based on some of the
data I've added.


Thanks,
Mark

In article < >, MarkY wrote:
[cut]
> So to recap:
> 1. I have malloc'd storage
> 2. I have written blocks of data into this storage (I know it's there
> because I can traverse the entire storage and output the information
> alas, by incrementing the pointer)
> 3. I need to jump from run location to another based on some of the
> data I've added.


Is this very different from

thing = memoryarray[memoryarray[i]];

or

thing = memoryarray[(int) memoryarray[i]];

or possibly

thing = memoryarray[converttoindex(&memoryarray[i])];

(where converttoindex() returns an int computed from the data
pointed to by the argument) ?


You're allowed to do that, but you're responsible for making
sure you store the right things at the right places with the
right types.


--
Andreas Kähäri

Andreas Kahari <ak+> wrote in message news:<slrnbocv98.r55.ak+ >...
> In article < >, MarkY wrote:
<snip>
>
> Is this very different from
>
> thing = memoryarray[memoryarray[i]];
>
> or
>
> thing = memoryarray[(int) memoryarray[i]];
>
> or possibly
>
> thing = memoryarray[converttoindex(&memoryarray[i])];
>
> (where converttoindex() returns an int computed from the data
> pointed to by the argument) ?
>
>
> You're allowed to do that, but you're responsible for making
> sure you store the right things at the right places with the
> right types.

Thanks Andreas. I was able to use a slightly modified version of Option 3.