Skip to main content

Learning Perl5i

I've been looking at the module perl5i, which puts a sideways twist on Perl, eliminating tons of boring boilerplate, and introduce many conveniences. In this case, the i eliminates complexity.

Installing perl5i installs a number of other modules as well, on the other hand life becomes better once they are installed.

If you don't have cpanm or one of the other improved CPAN installers, the simplest way is to install perl5i and its friends using the command

     sudo cpan perl5i

You may need to type in yes to have cpan  install dependencies. Some modules are needed only temporarily during installation, and you are asked whether you want them permanently installed. Perl modules don't take up very much space, so I always go for it. Installation is a bit different on Windows or Linux machines, but you can figure it out, you're a mighty Perl programmer!

One consideration is that major versions of perl5i may change in drastic ways. But you don't include perl5i; what you specify is perl5i::2. The newest module includes perl5i::0 and perl5i::1 as well, so old code is supported until you are ready to upgrade them.

The immediate benefit is that you no longer have to enable strictness. perl5i automatically provides

     use warnings;
  use strict;

So it costs you 14 characters to type

    use perl5i::2;

and straight off the bat it saves you 24 characters ....profit!


Oh, and it automatically activates features say, state and switch.


But wait! There's more! Not only does it slice and dice, it also julienes!

Well, no cutting anything in any shape ... but perl5i DOES provide autodie. If your open() doesn't work, the program dies; if the close() doesn't work, the program dies; if print() or a system() call or unlink() don't work, the program dies with an exception that turns into a string if you don't handle it.

Having a program die is an effective way to trigger in-house failure detection systems, such as Nagios. So simply doing the things you want, without checking return values, becomes a viable way to write a secure program that detects problems. If you need to catch and handle problems, perl5i provides Try::Tiny. There are other attempts at exception handling; any of them would be clearer than using eval. Try::Tiny is small, it does the job, and the intent is clear.

    try {
        open my $h, '<', '/does/not/exist';
    } 
    catch {
        say "the open() died with message $_";
    };

You can also add a finally block, to perform things that need to happen regardless of success or failure. The single weakness is that try is a statement, not a block, so it needs a semi-colon

So that's a major from installing perl5i, and we've barely gotten started.

Comments

Popular posts from this blog

Creating Perl5 Objects with Moxie

Having in the previous article prepared data types for car suits and card ranks, I can now combine them to provide a playing card class, using Stevan Little's Moxie module (version 0.04, so definitely early days.) The goal is to provide an object-oriented paradigm to the Perl 5 programming language which is more sophisticated, more powerful and less verbose than manually bless()-ing hashes. To achieve that goal it needs to be faster and light-weight compared to Moose. Currently, Moxie.pm and and MOP.pm are add-on modules, but eventually, when they are more complete, when the wrinkles have been ironed out, and when they have gained acceptance and a community of users, they might be merged into the Perl core.

One significant feature of Moxie is that it reduces boilerplate code. You don't have to specify warnigns or strict. As well, the features or the perl you are using are enabled, among them say, state, signatures, and post_deref.
A Simple Moxie Class package Card { …

Perl5, Moxie and Enumurated Data Types

Moxie - a new object system for Perl5 Stevan Little created the Moose multiverse to upgrade the Perl 5 programming language's object-oriented system more in line with the wonderfull world of Perl 6. Unfortunately, it's grown into a bloated giant, which has inspired light-weight alternatives Moos, Moo, Mo, and others. Now he's trying to create a modern, efficient OO system that can become built into the language.

I've seen a few of his presentations at YAPC (Yet Another Perl Conference, now known as TPC, The Perl Conference), among them ‎p5 mop final final v5 this is the last one i promise tar gz<. So I was delighted to recently see an announcement of the module Moxie, and decided to try implementing a card game.

While the package provides some POD documentation about the main module, Moxie, it doesn't actually explain the enum package, Moxie::Enum. But delving into the tests directory reveals its secrets.
Creating an Enum package Ranks { use Moxie::Enum; …

Adventures in Autovivification

Having recently started a new job, I was exposed to old code with multi-step tests against autovivification in multi-level hashes. You get used to the code you have seen, but in a new environment it‘s irritating and jarring.
Moose does not generally have the problem, first because class structure is pre-declared, because values are accessed using accessor functions rather than directly, and because responsibility is delegated down to attributes, avoiding long chains. On the other hand, Moose has it's own overhead, so hand-rolled objects, and bare structures still have their use.
If you don‘t protect against autovivification, then mis-spelling a key, or referencing keys which haven‘t been instantiated in this instance, causes those keys to instantly come into existence.
#!/usr/bin/perl use warnings; use strict; use Data::Dump 'dump'; use 5.024; my $var = {key1 => {key2 => {key3 => 'a'}}}; say dump $var; if ( $var->{key1}{key2}{key3b}[13]{foob…