Re: Parrot hijacks SIGINT

On 16 Mar 2004, at 06:36, Leopold Toetsch wrote:

>
> This is a snipped from the stress example program I posted some days 
> ago
> with an additional check if events are to be handled.  Both functions
> might not be in the extension interface[1].
>

Would it be possible to have a global variable that indicates if I have 
to poll for events, calling a function in-between every perl opcode is 
going to be very slow.

> Signals are converted to Parrot events and in the case of a program
> termination signal get broadcasted to all running interpreters.
>
> [1] BTW: Why does Ponie use the rather limited extension interface?

Because Dan said so, and because doing an include parrot.h in perl 
leads to one million or so cpp and gcc errors.

Arthur