Perl Object Environment: Difference between revisions

Revision as of 11:38, 6 September 2024

Latest revision as of 13:02, 3 January 2025

Line 4:

{{essay-like|date=October 2018}}

{{overly detailed|date=October 2018}}

{{manualhow-to|article|date=January 2017}}

}}

The '''Perl Object Environment''' ('''POE''') is a [[library (computing)|library]] of Perl modules written in the [[Perl]] [[programming language]] by [[Rocco Caputo]] et al.

From CPAN:

Line 19:

The POE::Kernel namespace contains a suite of functions which are plugged into the kernel itself. These loop abstractions are designed after POE's standardized event loop bridge interface - '''POE::Loop'''. These can be mixed and matched as needed to provide runtime services and a lean facility for [[interprocess communication]]. The basic functions are '''POE::Loop::Event''', '''POE::Loop::Poll''' and '''POE::Loop::Select'''. Also available are '''POE::Loop::Tk''' and '''POE::Loop::Gtk''' which offer hooks into other loop bridges in the external environment. If that isn't enough, the POE::Loop kernel abstraction provides reusable signal callbacks, time or alarm callbacks, and filehandle activity callbacks as well as administrative functions such as initializing, executing, and finalizing event loops.

There is also a higher level packaging framework - POE::Macro and a debugging utility for testing them called POE::Preprocessor. This framework has yielded '''POE::Macro::UseBytes'''.

:NOTE: As the Perl tradition mandates, POE is also a moving target.

Always check [[CPAN]] to see what new goodies the community has placed in the archive.