>Does this mean I can simply replace MemDeref with MemHandleLock?  If so,
why
>did datebook use MemDeref in the first place?
Almost. But you'll have to call MemHandleUnlock to reverse the locking
process.

I don't know why Datebook uses MemDeref.  Probably historical reasons that
no longer apply or are no longer recommended today.  In looking at our
internal source code repository, I see that Datebook was changed on 3/5/99
to no longer call MemDeref.

-- Keith Rollin



Reply via email to