This week, I released a new version of
Beam::Emitter. A lot has changed since
the first releases, so here's some details on all the new features.
Beam::Emitter is a role for turning your classes into event emitters. Being an
event emitter allows other classes to subscribe to important events from your
object. Subscribers can use these events to perform additional tasks, transform
your object's data, or otherwise extend and enhance your class. Beam::Emitter
makes your class extensible by allowing you to provide specific places for
custom code to run.
Since the 1.000 release last year, Beam::Emitter has gotten quite a few new
features and bug fixes to make it easier to use and safer for your code.
Continue reading Beam::Emitter v1.004 released...
A new trial of Log::Any (1.044) has been
This release has a couple changes that make Log::Any a bit more
- Passing in objects to formatted log methods now handles objects that
overload stringify correctly. Previously, these objects would be given
to Data::Dumper, which violates object encapsulation. Thanks Philipp
- The imported Log::Any object (
use Log::Any '$log') can now be named
Since CPAN Testers is still catching up
from its little bit of downtime a few weeks
ago, I won't be releasing this
as stable until I get some success reports in. So, you've got some time
to test this against your own codebase if you need to. Please report
any issues to the Log-Any Github
Since CPANTesters for Log-Any
are all showing green for last week's trial
I've pushed a new standard release of Log::Any 1.042 to
Continue reading Log::Any 1.042 Released...
I've just released a new Log::Any
trial release. This release improves performance immensely when there
are no log output adapters configured. This release also now returns the
formatted log string from logging methods, allowing the log message to
be used by a
Because of these changes, there is a very small chance of an
incompatibility: Log::Any logging methods used to return whatever the
configured adapter returned (this was undocumented and was not
a feature). Now they always return the formatted log message.
So if you depend on Log::Any, please give
a test run through and report any issues to the Log-Any Github
This year, I was invited to the Perl QA Hackathon in Rugby,
UK. It was wonderful to meet all
the Perl people I'd been interacting with all this time.
My goals going into the hackathon weren't that clear: I've recently
begun adopting the CPANTesters project,
and I had to take the opportunity to talk with its former leader,
Barbie, fix some current issues, and then...
While Barbie fixed the version summaries and Metacpan
I started work on an automated deploy for
CPANTesters using Rex, which
will allow for reproducible deployments and development virtual
machines, and I began keeping track of the project and future goals in
a CPANTesters project
which should help with keeping CPANTesters going as an open community project.
I'll be making future blog posts on both of these, though I've spoken
about Rex before.
Thanks to Barbie for 10 years of CPANTesters, and special thanks to
Capside for their donation, both monetary and
avian, as they sent Oriol Soriano to
help with some CPANTesters tasks.
And finally, thanks to all the other sponsors of the
their support, we couldn't do all the work we do on the Perl ecosystem.