はてなブックマーク

Earlier this week, I proposed that Module::Build be deprecated from the Perl 5 core. After some discussion, this proposal has been accepted by the Pumpking. I want to take a moment to discuss what this means, why I suggested it, and what I think Module::Build trail blazed for Perl 5. Deprecation means a warning in v5.19 and removal in v5.22 🔗︎ Soon, in Perl 5 version 19 (the current development s

The official Lancaster Consensus document is on Github. This blog post is an annotated review of it. The Lancaster Consensus 🔗︎ At the first Perl QA Hackathon in 2008 in Oslo, a number of QA and toolchain authors, maintainers and experts came together to agree on some common standards and practices. This became known as “The Oslo Consensus”. Five years later, at the 2013 Perl QA Hackathon, a simi

This post is a response to Neil Bower’s post Don’t release experiments to CPAN. Neil, respectfully, I disagree. The huge success of CPAN is, I think, in large part because it encouraged experimentation and alternatives. Suggesting people upload elsewhere (Github) and have module installers use that just creates barriers to participation and barriers to participation are the last thing that Perl ne

I like Path::Class, but it’s clunky and slow. So I wrote Path::Tiny to scratch my itch. It’s smaller (roughly half the lines of code), comes in a single file, and is generally faster. Among other things, it has lots of handy UTF-8 input and output methods. The downside is that it’s less portable and less extensible, but let’s be honest, most of us are developing only for Unix or Windows anyway. An

infrastructure as code automated! repeatable! testable! (no manual steps, checklist, etc.)

I’ve been using Test::More for so long that I sometimes forget about new features that have been added in the last couple years. If you’re like me and would like a refresher, here’s a list of five useful features that you might want to start using. Unless otherwise noted, you will need at least version 0.88 of Test::More. 1. done_testing instead of no_plan 🔗︎ If you don’t know how many tests you

I’ve recently been collaborating with Christian Hansen on HTTP::Tiny, a minimalist, HTTP/1.1 client library for Perl. For basic web client tasks like grabbing a single page or mirroring a file, it does the job in a fraction of the code that would be needed to install LWP::UserAgent. Because it has no non-core dependencies, it is ideal for what I need to get CPAN.pm to bootstrap itself with pure Pe

I’ve got too much going on this week to do much blogging, but I’m happy to say that my experiments teaching CPAN.pm to bootstrap local::lib look promising. During CPAN auto-configuration, when CPAN recognizes that the user doesn’t have write access to the Perl library directories, my experimental CPAN.pm offers to bootstrap local::lib after configuration is completed. Once this is done and release

Most of the time, you shouldn’t use Perl’s function prototypes. They aren’t function signatures the way you expect. Instead, they mostly help the parser understand how to interpret arguments using the right context. Here is a simple example: sub foo($) { say shift } The ‘$’ prototype says that foo takes a single argument in scalar context. Consider this: $ perl -wE 'sub foo($){say shift} @array=("

Andy just asked “What are you working on in Perl?" but rather than reply in a comment, I thought it would be a good Ironman post of my own, so here we go: CPAN Meta Spec version 2 – I released the final spec and will soon be looking to rally toolchain developers to implement it. CPAN Testers 2.0 – I launched CPAN Testers 2.0 Beta site, the eventual replacement for the current practice of sending C

Dear CPAN authors, It is with great pleasure that we present you with the release of the CPAN Meta Spec version 2. This document specifies the format for the next version of CPAN distribution metadata files – the META.yml and now META.json files found in most distributions on CPAN. Version 2 is the result of a call for proposals last year that resulted in 34 proposals and over 300 discussion email

The Perl community seems abuzz about the cool new cpanminus client by Tatsuhiko Miyagawa. After about two weeks of development, this is a reasonably functional CPAN client with just a fraction of the overhead, complexity and verbosity of the CPAN and CPANPLUS clients that come with the Perl core. It’s a remarkable achievement, not only technically, but in the reaction it has sparked. As one of the

I’ve recently released a development snapshot of Module::Build 0.35_01. This release implements MYMETA.yml. MYMETA.yml is just like META.yml, in that it follows the CPAN Meta Spec, but whereas META.yml is generated by the distribution author at packaging time, MYMETA.yml is generated by the end user at configure time after any dynamic dependencies are known. This is the new approach agreed to in p

In a perfect world, I would never blog about version numbers in Perl. Version numbers should be boring. No one should have to think about how they specify or check a version number. Perl programming makes things easy, not hard, right? Unfortunately, version numbers in Perl aren’t boring and easy. Instead, they are complicated and confusing. Every Perl programmer needs to understand at least some o

At the Perl QA hackathon, Andreas Koenig, the maintainer of PAUSE, demonstrated a way to decrease the lag between new distribution uploads to PAUSE and syndication to CPAN mirrors.  (See File::Rsync::Mirror::Recent on CPAN for details).   Running minicpan against a one of the new, fast updating mirrors results a very fresh minicpan, but, until now, only for regular releases, not for alpha developm

Copyright © 2006 David A. Golden How to capture output in Perl David Golden dagolden@cpan.org Spring 2009 NOT 1 Copyright © 2009 David A. Golden "How do I capture output in Perl?" 2 Copyright © 2009 David A. Golden Simple question 3 Copyright © 2009 David A. Golden Deceptively simple 4 Copyright © 2009 David A. Golden So what's easy? 5 Copyright © 2009 David A. Golden STDOUT of a command 6 Copyrig