Re: Some thoughts WRT exceptions, events, and threads

(I apologize profusely for the formatting--I'm writing this on a rather primitive webmail system.) Disclaimer: this is all from possibly faulty memory, except where it's pure speculation. Leopold Toetsch: I'd like to layout some thougts, which get quite dim, when it comes to threads. So there a

Re: Some thoughts WRT exceptions, events, and threads

> Yep. But when it comes to multithreading you can't assume the same > behavior on e.g. single or multiprocessor systems anway. > leo Sounds like a user-land implementation should be default then, to guarentee consistancy across hardware let alone machines. Software targeted for specific uses c

Re: Some thoughts WRT exceptions, events, and threads

K Stol <[EMAIL PROTECTED]> wrote: > (... skipping (1) and (2) ...) >> 3) Threads > Is 'the underlying model' the implementation of the OS running parrot (as > oppposed to a self-made system, On Linux there are many threading libs. E.g. pth (GNU portable threads) and pthread (POSIX threads). The

Re: Some thoughts WRT exceptions, events, and threads

(... skipping (1) and (2) ...) > 3) Threads > The underlaying model are posix threads if available. This implies > that all interpreter data are shared by default. So we'll need per > thread data: interpreter, prederef & JIT code ... Is 'the underlying model' the implementation of the OS running

Some thoughts WRT exceptions, events, and threads

I'd like to layout some thougts, which get quite dim, when it comes to threads. So there are a lot of questions. 1) Exceptions There are 3 kinds of exception sources: - hard: e.g. SIGFPE, SIGHUP. They get catched by signal handlers[1] - soft: internal_exception() - user: a C opcode signals a warnin

Re: Events and threads

On Sat, 06 Jan 2001 13:09:47 -0500, Dan Sugalski wrote: >Okay, here's a big question that ties the two major pains we have in perl >6--how do we tie threads and events together? > >* Can all events be delivered to any thread? Yes, but in practice events probably would only be delivered to threa

Events and threads

Okay, here's a big question that ties the two major pains we have in perl 6--how do we tie threads and events together? * Can all events be delivered to any thread? * Will events be delivered only to the thread that caused them? If so, what about threadless events? (Say, signals from the outsid