calling events together

[cooper]

calling events together

[cooper]

Evented::Object 5.62 allows multiple callbacks to have the same name. It intelligently guesses which callback you are referring to by considering the object and event name to which the callbacks were attached.

For Ferret this means that things like before, after, cancel, etc. should work as expected when calling events together. If you say before :someName but multiple events have a callback named :someName, it will refer to the one on the same event. But if :someName only exists on an event other than the one to which the callback is attached, it will refer to that one. So basically, it's smart.

Something else neat is that all :default callbacks have the same priority. So if you say before :default, the callback will be executed before all default functions involved in the multi-call.

[cooper]

so now that Event.callTogether() is functional, the next step is to create some decent-looking way to do something similar to Evented::Object's event listeners. For example, in the IRC::Bot code currently the PRIVMSG handler is manually added to each connection. Instead, there needs to be some way to make the bot "listen to" the connection.

[cooper]

OK I'm facing another issue. In Perl it is common to fire all events related to an object on that actual object. In Ferret, this would be pretty messy. It Ferret it's more common to store events in a separate object and then call them with _this set to the desired evented object.

This means that in the case of the IRC bot, we would be attaching events to the $bot.handlers and $conn.handlers objects. So the bot handlers would need to "listen to" the connection handlers. Yet, there needs to be a way to access the bot object from the callbacks attached to $bot.handlers.

[cooper]

I'm thinking the new .*addListener() special method should accept any arguments which will be supplied to the callbacks coming from a certain object. In the case of the bot, this would look something like $conn.handlers.*addListener($bot.handlers, bot: $bot).

[cooper]

Note that this would result in the listenee holding a reference to the provided arguments until .*removeListener() is called.

[cooper]

Hmmm, should adding a listener also imply it is a parent? Not sure