> From: Jason Dawes [mailto:[EMAIL PROTECTED]]
> But does the memory manager automatically unlock the memory
> when freeing it?
Conceptually, I guess you could say that. But there is really no such thing
as "locked" and "unlocked" freed memory. Whether you are freeing a chunk
that is locked or one that is unlocked, the Memory Manager just tosses it
onto the free pile.
> After all, there should be some entry
> in a mapping from handle to pointer somewhere.
> This might cause problems later.
I don't quite understand the question. Do mean such a mapping may exist
inside the user's app, or do you mean inside the Memory Manager? (The
Memory Manager has no trouble keeping everything straight.) No matter how
the app keeps track of memory it has allocated, it needs to be implemented
so that it _never_ attempts to access _any_ chunk after that chunk has been
freed. If, say, one part of the app frees a chunk that some other part of
the app still mistakenly thinks is available, then that's just a good old
fashioned bug in the app.
-slj-
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
