Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

masak (6289)

masak
  (email not shown publicly)
http://masak.org/carl

Been programming Perl since 2001. Found Perl 6 somewhere around 2004, and fell in love. Now developing November (a Perl 6 wiki), Druid (a Perl 6 board game), pls (a Perl 6 project installer), GGE (a regex engine), and Yapsi (a Perl 6 implementation). Heavy user of and irregular committer to Rakudo.

Journal of masak (6289)

Sunday June 21, 2009
10:38 AM

Asking #perl about Modern Perl

[ #39158 ]

This is my first Perl 5 post ever. 哈哈

<masak> while I'm here, I'd like to talk about Modern Perl.
<masak> in y'all's opinion, what are the modules a Modern Perl 5 user should be aware of?
<masak> I'm thinking of things like Moose, List::Util, maybe Catalyst...
<claes> it all depends on what the task is
<lucs> masak: 5.10 in general maybe
<claes> using warnings, strict and perhaps indirect pragmas
<masak> I think things that we take for granted as good time-savers all qualify.
<masak> so maybe stuff like Getopt::Long too.
<claes> personaly I don't use Moose because I haven't had any use for it yet
<masak> for me as a Perl 6 user, it's not that difficult to see the use for Moose.
<masak> I saw a blog post recently that said that Moose even helped the blogger document things more succinctly.
<masak> that is, even when he wasn't using Moose, he was using habits gained from it to write better documentation.
<Hinrik> Perl::Critic, definitely
<claes> Devel::NYTProf
<Hinrik> some of the eventy things (AnyEvent, Coro, POE) too, if that's what your app requires
<Hinrik> and the various Test::* modules, of course
<masak> Hinrik: which ones, more exactly?
<Hinrik> Test::More usually works for me, along with some other specialized ones depending on the typo of app
<Hinrik> e.g. Test::Script to test if scripts compile
<Hinrik> masak: oh, and Devel::Cover is also quite helpful in determining test coverage
<cfedde> see also Modern::Perl
<cfedde> I think that the standard template will become 'use Modern::Perl; use Moose'

Feel the need to add something to the list? The comments are open.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • DateTime [cpan.org], Email::Sender [cpan.org], Parallel::ForkManager [cpan.org], SQL::Abstract [cpan.org], and TAP::Harness [cpan.org]
  • for some reason 'use Modern::Perl' makes me feel queasy.

    For one thing, it seems snide. For another, though the documentation suggests that in the future other modules might be added, it doesn't suggest how to resolve the case of different scripts that require different versions of the bundled modernity. I hope the plan is prettier than use Postmodern::Perl, then Really::Modern::Perl and finally I::Can't::Believe::It's::Not::Modern::Perl ;-P

    --

    osfameron

    • The best plan I've seen so far is to use a date as the argument to M::P's import method: use Modern::Perl 2009;