I've heard a few different things from Palm in the past on dilly-dallying
around in a shared library's sleep()/wake() entry point. The thesis is this
-- because they can be called from within an interrupt service provider
(ISP), you really shouldn't spend much time at all in either of them. If
you have a lot of stuff that needs to happen, post a key event and get out.
Then catch that key event in an EvtGetEvent() hook shortly, where you can
take your time doing whatever you need to do.
I've had to debug code that crashed because it spent too much time here.
I've also gotten away with doing quite a bit in these functions before I saw
any trouble.
Has anyone ever heard any numbers from Palm on this? Like, don't spend more
than 12 ms in the routine?
Thanks,
-jeff ishaq
The Windward Group
