perlfind - perldoc on steroids

Every time I use perldoc for any term slightly unusual, I struggle. Have you tried to use it to find UNITCHECK? Now you can. Instead of remembering which of these to use (and none of these will find UNITCHECK):

You can just type:

perlfind --all UNITCHECK

In the last case above, the --all is needed to do a brute force search. Ordinarily, you just do perlfind searchterm, regardless of whether it's a module name, function, variable, or faq keyword and it will return the first result found (searched in the order I just mentioned). Otherwise, it will tell you to use --all if you really want a brute force search to find out where that term is used.

Here's a gist I tossed out there. Patches welcome. I should bundle this up and put it on the CPAN (and handle older perldoc versions).

Migrating an Enterprise across 14 Perl Releases

Steffen Mueller will give a talk at YAPC::NA 2012 described as: is the world’s leading online travel agent for hotel reservations. It is a wildly successful enterprise that was built with Perl at its heart. The company’s IT team runs millions of lines of Perl code on thousands of servers.

In this presentation, we will outline how we migrate(d) one of the world’s biggest users of Perl across 14 stable releases of Perl from 5.8.5 to 5.14.2, why we did that, what bit us, and what we learned from it.

[From the YAPC::NA Blog.]

YACGR (yet another creepy grant report)

I mean creepy in the sense that results slowly creeping in. People who follow my tweets know that 2 smaller milestones are achieved: predefined subrules and regex quantifier are now all in place (in Index A and B). This was of course a byproduct of my upcoming Perl 6 Regex and Grammar talk.
So we not far away from 700 items in Index A (50 more than last time). Some bits other were done.

Hope you guys are not to impatient but since im doing this thing for years and still on it, its not far fetched that one day im ready with it. It's also like writing a book, which, when taken seriously, needs constant improvement. The quality and consistency of the entries grew all the time. They also explain some of the terms like LTM, role, runtime and so on. if you think that doesn't have to be in an index, please let me know.

User experiences with Marpa: some observations

When it comes to user experiences with Marpa, I confess to being a highly biased source. I hope the following observations will be useful nonetheless. (Marpa, for those new to this blog, is a new, powerful and fast parser and parsing algorithm. To learn more, check out its web page.)

Marpa does the job

If you've read user's accounts of work with BNF grammars over the years (I have studied many), you know they follow a familiar pattern. The user has some BNF. He then tries tool X (for X substitute yacc, bison, PEG, recursive descent, etc.) and finds that it almost works. Almost, but not quite. The rest of the account describes the user beating up his grammar in an effort to make it fit the tool. Perhaps 50% of the time, he reports that his effort was wasted.

Thank You Sponsors!

We’d like to thank our sponsors for stepping up to support us. We really couldn’t do this without their support.

You too could sponsor YAPC.

[From the YAPC::NA Blog.]

How to test an abstract builder?

Hi Perl blogosphere. Yes, today I’m talking into the camera.

I’m very pleased to have had my Perl Foundation Grant to develop Alien::Base funded and I have redoubled my efforts.

I have high hopes for this module as a tool to help authors provide the C libraries they need through CPAN far more easily than hand rolling an Alien:: module. As such I feel a deep urge to ensure that Alien::Base is robustly tested.

Unfortunately I’m finding that testing such a module is rather hard. Alien::Base is a very abstract concept. It only makes any sense when it is used as the base class for some other Alien:: module, and futher, THAT module is only fully realized when it is used by some other module which needs that C library.

YAPC::Asia Tokyo 2012

This year's YAPC::Asia Tokyo is going to be happening at 9/27, 9/28, and 9/29.

We're expecting Tim Bunce, Adam Kennedy and Larry Wall as guest speakers! I think there's no need to introduce these guys here... :)

We just got started with the preparations, so there isn't much to see, but we have a minimal website up (yes, it's going to be updated soon ish). To get a taste of what YAPC::Asia is all about, please check out my entry for YAPC::Asia Tokyo 2011, checkout the videos, or checkout our photos.

We hope to see more foreign guests coming, please keep this in your schedule! And contact me should you need any help getting to/around Japan!

Linode has blown my mind again by increasing their sponsorship...

Linode has blown my mind again by increasing their sponsorship of YAPC::NA 2012 to the Platinum level. I can’t say enough good about them, not only as a sponsor of YAPC, but also as a great hosting company. Thank you Linode!

Recently named by Inc. magazine as one of the top 500 fastest growing private companies in America, Linode delivers virtualized cloud services from six regions across the U.S., Europe, and Asia to some of the most innovative companies in the world, such as The Onion and Creative Commons. The company’s proven IaaS (Infrastructure as a Service) offering enables customers to deploy and manage Linux virtual servers in the Linode Cloud with the ability to scale deployments to meet business demands - paying only for what they use with no long-term commitments. For more information, visit

[From the YAPC::NA Blog.]

About is a common blogging platform for the Perl community. Written in Perl and offering the modern features you’ve come to expect in blog platforms, the site is run by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.