On Wed, Feb 02, 2000 at 10:47:43PM -0500, [EMAIL PROTECTED] wrote:
> NI> Ick - you did that too. If I had my time over again I would not
> NI> have done that in Tk - the constructor idea is fine, but
> NI> the implcit require is a pain. In particular you don't discover
> NI> that your app has not been correctly B::* compiled till
> NI> you try and run it and hit the execution pattern that needs the require.
>
> well that can be fixed easily. i am only in development. how many users
> of event.pm are there? it is classified as beta code as well.
>
> on the other hand, most event watchers are created at startup. so the
> chances of a long wait before a dynamic load triggers a compile error
> are slim. and there are a lot fewer of them than tk things to load so it
> is easier to manage and keep the compiler bugs out.
Nick, are you satisfied with Uri's comments? We *can* change Event if
folks feel strongly about it. It's not too troublesome to add this to
my codes:
require $_ for qw(Event::io Event::timer); # untested
--
"May the best description of competition prevail."
via, but not speaking for Deutsche Bank
