On Thu, Dec 16, 1999 at 04:56:38PM -0500, [EMAIL PROTECTED] wrote:
> I'm trying to create a new perl Event watcher type for a C++ messaging API
> that my company uses.
>
> Embedding the perl event loop, and creating watchers that mimic the behavior
> of the perl ones has been surprisingly easy.
Glad to hear it!
> However I see, from looking at
> Event::tcpsession and process.pm, that the Event::Watcher class has some
> "registry" functions. Is this what I think it is - some standard wrappers for
> custom watchers.
Yes.
> Is there a recommended way to use this (or is it Joshua's privilege, and I
> should keep out?).
I admit that I have not published interfaces for all the guts yet. The
reason is that I am waiting for folks to come up with legitimate
extensions.
> As far as I can see, the register function also creates a watcher constructor
> of the form:
>
> Modules::A::B ==> Event->B()
>
> ... this looks disaster bound if someone else writes Other::C::B.
Yes, but the problem will be detected at run-time. Incorrect code will
cause an exception.
> Is there a
> view on module naming conventions? Currently it seems to be Event::Foo::Bar
> etc.
I do not expect Event to require a CPAN size namespace. How many
different types of event watchers do you need?
> I realize that Event is still in flux, but I would rather not reinvent the
> wheel if it's not absolutely essential.
What strange application problem are you trying to solve?
--
"Never ascribe to malice that which can be explained by stupidity."
via, but not speaking for Deutsche Bank
