Tim Bunce <[EMAIL PROTECTED]> wrote: > We should distinguish between the Parrot core and the parrot > executable command. The parrot executable command can use the > extension interface to indicate that it wants signal handlers to > be installed.
That can of course be separate. Anyway, if Ponie wants to catch signals, it has to call CHECK_EVENTS(). This is similar to "Deferred signals" described in perlipc. > Embedding parrot is an important goal. It seems inappropriate for > the parrot core to alter the state of the process, like installing > signal handlers, without providing some way for that to be disabled. As said: That's test code in an early stage. Which is good - it shows problems early ;) leo
