>Does this mean I can simply replace MemDeref with MemHandleLock?
>If so, why did datebook use MemDeref in the first place?
This was done back before Palm had a good profiler. It was suspected that
there might be a performance problem.
It turns out that even though MemHandleLock can take some time, it isn't
noticeable in those cases. It also ties the app's code to how the current
memory system works by relying on how it's designed internally. Lastly,
Palm is aware the many folks look at the PIM code for examples (which is
great). Given all that we're trying to clean out the MemDeref usage.
-Roger Flores
