Does this mean I can simply replace MemDeref with MemHandleLock? If so, why
did datebook use MemDeref in the first place?
Thanks,
Dan
-----Original Message-----
From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, April 27, 1999 2:13 PM
To: [EMAIL PROTECTED]
Subject: Re: datebook and emulator question
Yes, use of MemDeref is not recommended. That's why it's in a private
header file (MemoryPrv.h) and protected with the NON_PORTABLE preprocessor
symbol.
To get the pointer associated with a handle, call MemHandleLock.
-- Keith Rollin
-- Palm OS Emulator engineer
Daniel Zucker <[EMAIL PROTECTED]> on 04/27/99 01:56:11 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: (Keith Rollin/HQ/3Com)
Subject: datebook and emulator question
I am running Datebook on PalmOS 2.0 using the 21d26 emulator.
Everything seems to work OK, but the emulator complains (warning only,
not an error) when it encounters a MemDeref command.
Can someone tell me what's up with that? Is this not a recommended
programming practice? What is the correct way to do it?
Thanks,
Dan
PS If you're wondering why I'm running PalmOS 2.0, the answer is that I
don't own a Palm III or newer.
