Nicholas Clark wrote:
What is the state of signals and events support? As far as I can tell from
watching which perl 5 regression tests fail or hang under parrot, currently
parrot can't behave as a passive embedding target - it assumes that it needs
to take ownership of all signals.
Parrot curr
On Friday, January 23, 2004, at 09:39 , Dan Sugalski wrote:
At 12:05 PM +0100 1/23/04, Leopold Toetsch wrote:
So my local src/events.c does:
1) block all signals before any thread creation
2) install an event handler for SIGINT
3) start the event handler thread
4) start an IO handler thread, whi
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> All this stuff needs to get out of events.c at some point, and we
> probably better do it now rather than later.
Yeah. Thought about that too. I'm a bit unhappy with the current
config/gen/platform/* files.
Me thinks that we should do:
- s/generic/posix/
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
[ and another f'up myself ]
> The IO thread can then generate a SIGINT_EVENT and pthread_signal the
> event thread. And it could wait on various file-handles and on an
> internal pipe, which can be used to communicate file-handles to be
> waited on to th
At 12:05 PM +0100 1/23/04, Leopold Toetsch wrote:
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
The event handler thread is waiting on a condition, so the only
possibility seems to be the latter option, that is run another thread
that does nothing but sigwait(3).
While pressing $send_button I real
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> The event handler thread is waiting on a condition, so the only
> possibility seems to be the latter option, that is run another thread
> that does nothing but sigwait(3).
While pressing $send_button I realized, that there is another option and
- of co
