Moosex poe

Description

This is a small wrapper that ties together a Moose class with POE::Session, and gives you an event sugar function to. Package: perl-MooseX-POE . Summary: A Instance Metaclass for MooseX::​POE Description: MooseX::POE is a Moose wrapper around a POE::Session. MooseX::POE::Meta::Trait::Object - The base class role for MooseX::POE package Counter; use MooseX::Poe; has name => (isa => 'Str'.

Packager: Fedora Project. Url: oesteonline.info Summary: Illicit Love Child of Moose and POE. Package: perl-MooseX-POE . Summary: A Instance Metaclass for MooseX::​POE Description: MooseX::POE is a Moose wrapper around a POE::Session. MooseX::POE::Meta::Trait::Object - The base class role for MooseX::POE package Counter; use MooseX::Poe; has name => (isa => 'Str'.

Modules. MooseX::POE - The Illicit Love Child of Moose and POE; MooseX::POE​::Aliased - A sane alias attribute for your MooseX::POE objects. p5-MooseX-POE The Illicit Love Child of Moose and POE ART10 GPLv1+; Description: MooseX::POE::Object is a Moose wrapper around a POE::Session. MooseX::POE::Role(3pm), User Contributed Perl Documentation This is what MooseX::POE is to Moose but with Moose::Role.






A cheap alias for moosex same POE::Kernel function which will gurantee posting to the object's session. See that module for the documentation for. Below is a list of methods on that class so you know what to look for:.

MooseX::Declare support is still "experimental". Meaning that I don't use it, I don't have any code that uses it, and thus I can't adequately say that it won't cause monkeys to moosex out of any orifices on your body beyond what the tests and the SYNOPSIS cover.

The method moosex doesn't seem to moosex as expected. This poe an integration issue that is being resolved poe I want to wait for MooseX::Declare to gain some more polish poe their slurpy arguments. This means that you'll get a keyword clash between the features that Poe handles for you and the features poe Moose handles. To moosex around this you'll need to write:.

For more information on module installation please visit the detailed CPAN moosex installation guide. That said there are a few caveats that have turned up during testing.

CPAN Mirrors. Fork metacpan. Hosting generously provided by:. Keyboard Shortcuts. Global s Focus search bar? Poe up this help dialog Moosex g p Go to pull requests g i go to github issues only if github is poe repository.

MooseX::Declare support is still "experimental". Meaning that I don't use it, I don't have any code that uses it, and thus I can't adequately say that it won't cause monkeys to fly out of any orifices on your body beyond what the tests and the SYNOPSIS cover. The method keyword doesn't seem to work as expected. This is an integration issue that is being resolved but I want to wait for MooseX::Declare to gain some more polish on their slurpy arguments.

This means that you'll get a keyword clash between the features that MooseX::Declare handles for you and the features that Moose handles. To work around this you'll need to write:. For more information on module installation please visit the detailed CPAN module installation guide.

That said there are a few caveats that have turned up during testing. However, if your colleagues are Java-infected, they might prefer a singleton.

Also, if you have an existing class that isn't a singleton but should be, using MooseX::Singleton is the easiest way to convert it. There are literally dozens of other extensions on CPAN. This is a list of extensions that you might find useful, but we're not quite ready to endorse just yet. MooseX::Declare is based on Devel::Declare , a giant bag of crack originally implemented by mst with the goal of upsetting the perl core developers so much by its very existence that they implemented proper keyword handling in the core.

As of perl5 version 14, this goal has been achieved, and modules such as Devel::CallParser , Function::Parameters , and Keyword::Simple provide mechanisms to mangle perl syntax that don't require hallucinogenic drugs to interpret the error messages they produce.

If you want to use declarative syntax in new code, please for the love of kittens get yourself a recent perl and look at Moops instead. This extension helps you build a type library for your application. It also lets you predeclare type names and use them as barewords. One nice feature is that those bareword names are actually namespaced in Moose's type registry, so multiple applications can use the same bareword names, even if the type definitions differ. This extension builds on top of MooseX::Types to let you declare complex data structure types.

This extension provides class attributes for Moose classes. The declared class attributes are introspectable just like regular Moose attributes. Note however that this class attribute does not inherit like a Class::Data::Inheritable or similar attribute - calling. Additionally, class data is usually The Wrong Thing To Do in a strongly OO program since it makes testing a lot harder - consider carefully whether you'd be better off with an object that's passed around instead.

This is a role that provides a number of methods useful for creating a daemon, including methods for starting and stopping, managing a PID file, and signal handling. If you find yourself wanting a role that customizes itself for each consumer, this is the tool for you. With this module, you can create a role that accepts parameters and generates attributes, methods, etc.