anyevent::impl::cocoa(3pm) [debian man page]

AnyEvent::Impl::Cocoa(3pm)				User Contributed Perl Documentation				AnyEvent::Impl::Cocoa(3pm)

NAME

       AnyEvent::Impl::Cocoa - AnyEvent adaptor for Cocoa::EventLoop

SYNOPSIS

	   use AnyEvent;
	   use Cocoa::EventLoop;

	   # do something

DESCRIPTION

       This module provides NSRunLoop support to AnyEvent.

       NSRunLoop is an event loop for Cocoa applications, wrapped by Cocoa::EventLoop. By using this module, you can use Cocoa based API in your
       AnyEvent application, or AnyEvent within Cocoa applications.

       It does not support blocking waits.

BUGS

       Right now, Cocoa::EventLoop (and this module) are in an early development phase and has some shortcomings and likely bugs.

       For example, there seems to be no way to just handle a single event with Cocoa (is there nothing they can implement properly?), so this
       module currently wakes up at least ten times a second when waiting for events. Also, events caused by timers might get delayed by up to 0.1
       seconds.

AUTHORS

       Daisuke Murase <typester@cpan.org>, Marc Lehmann <schmorp@schmorp.de>.

COPYRIGHTS

	  Copyright (c) 2009 by KAYAC Inc.
	  Copyright (c) 2010,2011 by Marc Lehmann <schmorp@schmorp.de>

perl v5.14.2							    2012-04-08						AnyEvent::Impl::Cocoa(3pm)

AnyEvent::Impl::Irssi(3pm)				User Contributed Perl Documentation				AnyEvent::Impl::Irssi(3pm)

NAME

       AnyEvent::Impl::Irssi - AnyEvent adaptor for Irssi

SYNOPSIS

	  use AnyEvent;

	  # this module gets loaded automatically when running under irssi

DESCRIPTION

       This module provides transparent support for AnyEvent. You don't have to do anything to make Irssi scripts work with AnyEvent.

       Limitations of this backend and implementation details:

       o   This backend does not support blocking waits.

	   That means you must set a callback on any condvars, or otherwise make sure to never call "recv" on a condvar that hasn't been signalled
	   yet.

       o   Child exits will be handled by AnyEvent.

	   AnyEvent will take over child handling, as Irssi only polls for children once/second and cannot handle unspecific child watchers.

	   This should have no negative effect, as AnyEvent will emit a pidwait signal just like irssi itself would.

       o   Artificial timer delays.

	   Irssi artificially enforces timers to have at least a 10ms delay (by croaking, even).

	   This means that some applications will be limited to a rate of 100Hz (for example, Coro::AnyEvent thread scheduling).

       o   Irssi leaks memory like hell.

	   Yeah.

       Apart from that, documentation is notoriously wrong (e.g. file handles are not supported by "input_add", contrary to documentation),
       hooking into irssi has to be done in... weird... ways, but otherwise, Irssi is surprisingly full-featured (for basically being a hack).

SEE ALSO

       AnyEvent, Irssi.

AUTHOR

	Marc Lehmann <schmorp@schmorp.de>
	http://anyevent.schmorp.de

perl v5.14.2							    2012-04-08						AnyEvent::Impl::Irssi(3pm)