Mel and anyone else.

>>Now, how does one access memory via a handle without dereferencing it first?
>
>Via a pointer :

That's dereferencing! Using a pointer _is_ dereferencing. That was my point.

---
>myPtr&=[myHandle&)
>blockmove myPtr&,@mynewVar,2:'      deref a handle to a pointer
>
>offSet&=0
>blockmove [myHandle&)+offSet&,@mynewVar,2:' copies two bytes from memory
>
>In the second example., it doesn't matter if memory moves in the second
>example, because you reference it from the handle anyway. If the first one
>moves, well that could produce interesting results.
>
>Mel Patrick - theWabbitGuy - mel@...


Okay, I'm totally confused. With the exact code given (first example v.
second given) what conditions would cause memory to move? In other words,
when code like this happens:

   myPtr&=[myHandle&)              '      deref a handle to a pointer
   blockmove myPtr&,@mynewVar,2:

What in the world could/would cause memory to move between the time you get
the pointer and when you do a block move?

Is memory something that can move at any time without cause? Or is it
something that can move when we do something to memory that alerts the
memory manager?

I would really like to know. Anyone?

tedd

___________________________________________________________________
<mailto:tedd@...>	               http://sperling.com/