2008/11/20 Michael Rueger <[EMAIL PROTECTED]>: > Igor Stasenko wrote: > >> If i remember correctly, an interrupt semaphore is used to awake a >> process which watching for interrupts. >> And indeed, when key combination matching an interrupt key code, >> it calls setInterruptPending(), which is then eventually leads to >> signaling a semaphore which registered as interrupt semaphore. >> You can't handle it on image side, because you may not have chance to >> get to it (if there's another process running on same or higher >> priority than event ticker process). >> While in VM, regardless what image does, it periodically checks for >> interrupts, and during handling OS events, it checks if an interrupt >> key pressed, and if so, then signals the semaphore. >> At least, this is how it looks on Win32. > > The question really was if it is in the VM but rather if it (still) should > be in the VM. > After some discussions with John I'm pretty sure we can remove the interrupt > semaphore code from the VM. For now that would mean that the image code > still referring to it should/can be removed. >
In this case, i'd like to read John's reasoning, why its safe to remove it from VM. >From my perspective , it should stay, because you can't imitate same behavior on language side safely. > Michael > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
