>>>>> "NI" == Nick Ing-Simmons <[EMAIL PROTECTED]> writes:
NI> Joshua N Pritikin <[EMAIL PROTECTED]> writes:
>> It isn't too bad. Only the Event package has a custom AUTOLOAD
>> function. It's purpose is to magically make:
>>
>> my $w = Event->watcher_type(...);
>>
>> Short hand for:
>>
>> require Event::watcher_type;
>> my $w = Event::watcher_type->new(...);
>>
>> Hm. Maybe that should be in the documentation somewhere...
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.
uri
--
Uri Guttman --------- [EMAIL PROTECTED] ---------- http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page ----------- http://www.sysarch.com/cgi-bin/perl_books
The Best Search Engine on the Net ---------- http://www.northernlight.com
