My Favourite Test::* Modules
If you don’t test your code, what makes you think it works?! Here are some of my favourite modules for testing Perl code….
Year: 2014
New “Woolly & Tig” Special
There was a surprise one-off Woolly & Tig episode this morning. I hadn’t seen it advertised anyway, so it was a surprise to me.
There will apparently be a Christmas special this year too. And some unspecified others during the year.
Andy’s Dinosaur Adventures
At the moment my son is really loving Andy’s Dinosaur Adventures, which I must admit is pretty well-made (even though we all miss Kip).
The premise of the show is that Andy is now working in “the National Museum” (most of the interior shots seem to be from the Natural History Museum in London; some of […]
Towards Type::Tiny 1.000000
Type::Tiny has been knocking around in some shape or another for almost a year now. It’s certainly grown a lot since its first commit. The distribution probably no longer merits the “Tiny” name, though the lead module itself is…
Introducing warnings::MaybeFatal
OK, so you’ve written your module like this: package MyUtils; use strict; use warnings FATAL => qw( all ); sub frobnicate { … } 1; It passes its test suite, and all is fine and dandy. You use the frobnicate…
Planet Moose – January 2014
Welcome to Planet Moose, a brief write up on what’s been happening in the world of Moose in the past month, for the benefit of those of you who don’t have their eyes permanently glued to the #moose IRC…
Horizontal Reuse: An Alternative to Inheritance
In class-based object-oriented programming, when there are classes that appear to share some functionality, this is often a time when people will refactor them into two subclasses of a common base class, avoiding repetition.
For example, in my farm model the Horse class and the Tractor class each implement a pull_plough method. (American readers might prefer pull_plow.) So this method is a candidate to split out into a Hitchable class for Horse and Tractor to each inherit from.
This would have nice benefits for polymorphism. I’ll be able to pass an object to my Farmer which will only need to check that the object inherits from Hitchable rather than having a hard-coded list of classes like Horse and Tractor that it knows are acceptable.
PAUSE is no longer paused
PAUSE was down. Now it’s up. Yay! Well done, and thank you to everyone who helped restore, and indeed help with the day-to-day running of PAUSE….
Introducing Sub::Trigger::Lock
Sub::Trigger::Lock is a workaround for the problem that Moose read-only attributes aren’t really read-only; at least, not in the way that people might expect them to be. Here’s an example: package Foo { use Moose; has bar => (is…
Planet Moose – December 2013
Happy new year, and welcome to Planet Moose, a brief write up on what’s been happening in the world of Moose in the past month, for the benefit of those of you who don’t have their eyes permanently glued…
