> "DLN" == David L Nicol <[EMAIL PROTECTED]> writes:
DLN> This too is something that would be very easy to do in
DLN> everything-is-an-exception world. All events throw "EVENT-whatever"
DLN> exceptions, and there you are.
That is a nasty and expensive way of doing something 'simple'.
And I
> "DLN" == David L Nicol <[EMAIL PROTECTED]> writes:
DLN> This too is something that would be very easy to do in
DLN> everything-is-an-exception world. All events throw "EVENT-whatever"
DLN> exceptions, and there you are.
and how do you dispatch on those events? an event loop should a
This too is something that would be very easy to do in
everything-is-an-exception world. All events throw "EVENT-whatever"
exceptions, and there you are.
--
David Nicol 816.235.1187 [EMAIL PROTECTED]
ll win.
>
>So the question I put to you all is, would it make sense for Perl to
>have a common event loop from which all other modules can then draw,
>thus avoiding the current state of conflict?
Absolutely.
The architecture of Tk applications will change considerably, for the better.
-
C and POE) the one who's main loop
MGS> starts up first will win.
MGS> So the question I put to you all is, would it make sense for Perl to
MGS> have a common event loop from which all other modules can then draw,
MGS> thus avoiding the current state of conflict? Or will a stab
Perl to
have a common event loop from which all other modules can then draw,
thus avoiding the current state of conflict? Or will a stable
threading implementation provide the equivalent?
PS This seemed like the right place to post this, other than
perl6-language which is stretched as
