> > http://www.cliedeveloper.com/spotlight/kinoma1.html
> >
> > IMHO it's a good tutorial on working with semaphores and blocks
> > larger than 64k...
>
> This is NOT good.
> MemSemphore issues aren't even mentioned in the official Palm-OS sdk.
> (when I remember right...)
yes, you do remember right. it is an undocumented API call that only
surfaced because it was inside a .h file in the SDK *g*
> Sony should care more about the things they publish, reading that
> article sounds like "MemSemaphore - used every day, don't care
> about the consequences ... "
anyone who has used a PalmSim with a debug rom will know that your
application will fail nicely when you call these routines. we use
them *only* when we know we can, mainly:
DmWrite(...);
is effectively:
MemSemaphoreReserve(true);
MemMove(...);
MemSemaphoreReserve(false);
adding some checks to make sure your not over-writing memory that
your not intending to. the big warning is that doing this is that
you can *overwrite* memory which isn't yours.
ie: you can zap the address book/applications etc..
causing serious issues/data loss
you should never use this API - unless you are 100000% sure you
know what you are doing; and, Palm/PalmSource plans to remove this
API eventually, dont expect it to hang around for long.
---
Aaron Ardiri [EMAIL PROTECTED]
CEO - CTO +46 70 656 1143
Mobile Wizardry http://www.mobilewizardry.com/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
