Now that I have (I think) a reasonable solution to the segmenting problem (a rather nifty extension to cproto for a different purpose which happens to extend quite well to the problem of assigning functions to segments), I've decided to get serious about porting my project, CalcRogue, to PalmOS. But first, there's a rather fundamental architecture issue which is bothering me.
WHY does everyone put the event loop at the base of the call stack?
Seems to me, it makes a lot more sense to write as one would a curses program with blocking input, only instead of calling getch(), call a function with the event loop in it. On getting a keypress, return from the event loop with the key; and if forced to quit, do it using a nonlocal return. But I've never seen it done this way, even when porting programs written with lots of blocking input.
So why does no one do this? Am I missing something?
-- CalcRogue: TI-89, TI-92+, Windows & Linux. <http://calcrogue.jimrandomh.org/>
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
