On Tue, 27 Apr 1999 [EMAIL PROTECTED] wrote:
> >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.
It looks like Datebook was using it because it helped the code flow to use
a hypothetical "MemPtrFromLockedHandle()" function, as MemDeref() was, at
one point, I guee.
> 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
--
Kenneth Albanowski ([EMAIL PROTECTED], CIS: 70705,126)
