Object::Event(3pm) | User Contributed Perl Documentation | Object::Event(3pm) |
Object::Event - A class that provides an event callback interface
Version 1.23
package foo; use Object::Event; our @ISA = qw/Object::Event/; package main; my $o = foo->new; my $regguard = $o->reg_cb (foo => sub { print "I got an event, with these args: $_[1], $_[2], $_[3]\n"; }); $o->event (foo => 1, 2, 3); $o->unreg_cb ($regguard); # or just: $regguard = undef;
This module was mainly written for AnyEvent::XMPP, AnyEvent::IRC, AnyEvent::HTTPD and BK to provide a consistent API for registering and emitting events. Even though I originally wrote it for those modules I released it separately in case anyone may find this module useful.
For more comprehensive event handling see also Glib and POE.
This class provides a simple way to extend a class, by inheriting from this class, with an event callback interface.
You will be able to register callbacks for events, identified by their names (a string) and call them later by invoking the "event" method with the event name and some arguments.
There is even a syntactic sugar which allows one to call methods on the instances of Object::Event-derived classes, to invoke events. For this feature see the "EVENT METHODS" section of this document.
In the first version as presented here no special performance optimisations have been applied. So take care that it is fast enough for your purposes. At least for modules like AnyEvent::XMPP the overhead is probably not noticeable, as other technologies like XML already waste a lot more CPU cycles. Also I/O usually introduces _much_ larger/longer overheads than this simple event interface.
There are 4 predefined aliases:
before => 1000 ext_before => 500 ext_after => -500 after => -1000
See also the "reg_cb" method for more information about aliases.
The return value $guard will be a guard that represents the set of callbacks you have installed. You can either just "forget" the contents of $guard to unregister the callbacks or call "unreg_cb" with that ID to remove those callbacks again. If "reg_cb" is called in a void context no guard is returned and you have no chance to unregister the registered callbacks.
The first argument for callbacks registered with the "reg_cb" function will always be the master object $obj.
The return value of the callbacks are ignored. If you need to pass any information from a handler to the caller of the event you have to establish your own "protocol" to do this. I recommend to pass an array reference to the handlers:
$obj->reg_cb (event_foobar => sub { my ($self, $results) = @_; push @$results, time / 30; }); my @results; $obj->event (event_foobar => \@results); for (@results) { # ... }
The order of the callbacks in the call chain of the event depends on their priority. If you didn't specify any priority (see below) they get the default priority of 0, and are appended to the other priority 0 callbacks. The higher the priority number, the earlier the callbacks gets called in the chain.
If $eventname1 starts with 'before_' the callback gets a priority of 1000, and if it starts with 'ext_before_' it gets the priority 500. 'after_' is mapped to the priority -1000 and 'ext_after_' to -500.
If you want more fine grained control you can pass an array reference instead of the event name:
($eventname1, $prio) = ('test_abc', 100); $obj->reg_cb ([$eventname1, $prio] => sub { ... });
Please note that an event can be stopped and reinvoked while it is being handled.
See also the specification of the before and after events in "reg_cb" above.
NOTE: Whenever an event is emitted the current set of callbacks registered to that event will be used. So, if you register another event callback for the same event that is executed at the moment, it will be called the next time when the event is emitted. Example:
$obj->reg_cb (event_test => sub { my ($obj) = @_; print "Test1\n"; $obj->unreg_me; $obj->reg_cb (event_test => sub { my ($obj) = @_; print "Test2\n"; $obj->unreg_me; }); }); $obj->event ('event_test'); # prints "Test1" $obj->event ('event_test'); # prints "Test2"
It returns false if that is not the case.
You can define static methods in a package that act as event handler. This is done by using Perl's attributes functionality. To make a method act as event handler you need to add the "event_cb" attribute to it.
NOTE: Please note that for this to work the methods need to be defined at compile time. This means that you are not able to add event handles using "AUTOLOAD"!
NOTE: Perl's attributes have a very basic syntax, you have to take care to not insert any whitespace, the attribute must be a single string that contains no whitespace. That means: "event_cb (1)" is not the same as event_cb(1)!
Here is an example:
package foo; use base qw/Object::Event/; sub test : event_cb { print "test event handler!\n" } package main; my $o = foo->new; $o->test (); # prints 'test event handler!' $o->event ('test'); # also prints 'test event handler!'!
In case you want to set a priority use this syntax:
sub test : event_cb(-1000) { ... }
Or:
sub test : event_cb(after) { ... }
You may want to have a look at the tests of the Object::Event distribution for more examples.
If you want to define multiple event handlers as package method you can use the "event_cb" attribute with an additional argument:
package foo; use base qw/Object::Event/; sub test : event_cb { # default prio is always 0 print "middle\n"; } sub test_last : event_cb(-1,test) { print "after\n"; } sub test_first : event_cb(1,test) { print "before\n"; } package main; my $o = foo->new; $o->test (); # prints "after\n" "middle\n" "before\n" $o->event ('test'); # prints the same $o->test_first (); # also prints the same
NOTE: Please note that if you don't provide any order the methods are sorted alphabetically:
package foo; use base qw/Object::Event/; sub test : event_cb { # default prio is always 0 print "middle\n"; } sub x : event_cb(, test) { # please note the empty element before the ','! print "after\n"; } sub a : event_cb(, test) { print "before\n"; } package main; my $o = foo->new; $o->test (); # prints "after\n" "middle\n" "before\n" $o->event ('test'); # prints the same $o->x (); # also prints the same
The ordering of how the methods event handlers are called if they are all defined for the same event is strictly defined:
There exists a package global variable called $DEBUG that control debugging capabilities.
Set it to 1 to produce a slightly extended "events_as_string_dump" output.
Set it to 2 and all events will be dumped in a tree of event invocations.
You can set the variable either in your main program:
$Object::Event::DEBUG = 2;
Or use the environment variable "PERL_OBJECT_EVENT_DEBUG":
export PERL_OBJECT_EVENT_DEBUG=2
Robin Redeker, "<elmex at ta-sa.org>", JID: "<elmex at jabber.org>"
You can find documentation for this module with the perldoc command.
perldoc Object::Event
You can also look for information at:
<http://annocpan.org/dist/Object-Event>
<http://cpanratings.perl.org/d/Object-Event>
<http://rt.cpan.org/NoAuth/Bugs.html?Dist=Object-Event>
<http://search.cpan.org/dist/Object-Event>
Thanks go to:
- Mons Anderson for suggesting the 'handles' method and the return value of the 'event' method and reporting bugs.
Copyright 2009-2011 Robin Redeker, all rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
2018-03-31 | perl v5.26.1 |