Event: DevMob 2010

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Event: DevMob 2010
# 1  
Old 01-26-2010
Event: DevMob 2010

Register for Dev Mob 2010 - free London conference/barcamp giving developers interested in portable devices the opportunity to discuss their issues and find solutions.

If you would like to suggest or host a session (or just participate) on any kind of mobile development issue, please register at DevMob 2010 - Uniting mobile application developers in London

Event details:
3rd February 2010
10am-5pm
Science Museum, South Kensington, London
Registration is free and refreshments will be provided!

Plus: chance to win a netbook courtesy of ASUS (event sponsors)
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
AnyEvent::Impl::EventLib(3pm)				User Contributed Perl Documentation			     AnyEvent::Impl::EventLib(3pm)

NAME
AnyEvent::Impl::EventLib - AnyEvent adaptor for Event::Lib SYNOPSIS
use AnyEvent; use Event::Lib; # this module gets loaded automatically as required DESCRIPTION
This module provides transparent support for AnyEvent. You don't have to do anything to make Event work with AnyEvent except by loading Event::Lib before creating the first AnyEvent watcher. Note: the AnyEvent author has not found recent releases of Event::Lib to be even remotely working (not even the examples from the manpage or the testsuite work), so this event backend should be avoided (or somebody should step up and maintain it, hint, hint). The Event::Lib module suffers from the same limitations and bugs as libevent, most notably it kills already-installed watchers on a file descriptor and it is unable to support fork. These are not fatal issues, and are worked-around by this module, but the Event::Lib perl module itself has many additional bugs such as taking references to file handles and callbacks instead of making a copy or freeing still- allocated scalars, causing memory corruption and random crashes. Only Tk rivals it in its brokenness. This adaptor module employs the same workaround around the watcher problems as Tk and should therefore be avoided. (This was done for simplicity, one could in theory work around the problems with lower overhead by managing our own watchers). Event::Lib also leaks file handles and memory and tends to just exit on problems. It also doesn't work around the Windows bug of not signalling TCP connection failures. It also doesn't work with many special devices on Linux (/dev/random works, /dev/urandom fails, /dev/tty works, /dev/null fails and so on). Event::Lib does not support idle watchers. They could be emulated using low-priority timers but as the priority range (and availability) is not queryable nor guaranteed, and the default priority is likely the lowest one, this module cannot use them. Avoid Event::Lib if you can. SEE ALSO
AnyEvent, Event::Lib. AUTHOR
Marc Lehmann <schmorp@schmorp.de> http://anyevent.schmorp.de perl v5.14.2 2012-04-08 AnyEvent::Impl::EventLib(3pm)