• Commented on On the version number succeeding Perl 5
    “To comment on using the year as the version number I think there are two problems with that. First, it doesn’t really signify that Perl6 is not the successor.” I think this gets at the actual social problem behind all...
  • Commented on Perl 7
    I think the main trouble with the "perl 7" idea is that the perl-porters aren't interested. Maybe they'd go with the year-as-version idea. The discussion of the "perl7" idea from back in 2007:
  • Commented on How to write a test description
    Yup... Further, I would add that an optimistic description that implies success makes the test output hard to read: not ok 2 - things are working perfectly It's easy to miss the "not" when there's a long chunk of text...
  • Commented on De Morgan's laws in Perl
    I just wanted to say that this is a nice, solid little post... I went through the same thing myself recently: getting annoyed at the mathematical notation used in the wikipedia page, and then re-writing them as more familiar programmer's...
  • Commented on Request sent for String::Strip comaintainership
    The FAQ (already linked to by Mithaldu) seems to be saying you need to write to and bug them about it there. I say "seems to", because it's the kind of writing where they really don't want to tell...
  • Commented on What should be in core?
    I'm going to disobey orders and offer a tentative guess at the size of a "market segment": I think there's a large segment of perl programmers who effectively can't use a module unless it's included in core. To cater to...
  • Commented on Bovicide 5: Parse-time Error Reporting
    Larry Wall's 2009 "State of the Onion" talk (which unfortunately, unlike the old days, does not seem to be easily available on-line in any form) was largely about how Perl 6's error reporting was much better than a yacc-based language...
  • Commented on Why I don't write in Pascal
    My experience with Pascal matches Aristotle's. I wouldn't necessarily make fun of someone who was working in Pascal, but I might look at them funny and ask them why. In addition to it's crippled string handling, Pascal was famous for...
  • Commented on Naming Tests
    I wouldn't think this one would be controversial.. test names should indeed be descriptive (test file names probably should be also, though that's a slightly different subject). A problem I've had with test names though, is that if I accidentally...
  • Commented on While on humor... best error msg in a while
    You want some really funny error messages, try something like elisp. "Stringp error." No line number, no function name, just the alert that there's something wrong with a string somewhere. (It's a dynamic language, you see, and in order to...
Subscribe to feed Recent Actions from

  • CosmicNet commented on Perl 7

    I believe that such action would be a real nail in the coffin. After all the talk of Perl 6 being the language of the future, people see a Perl 7 release, think "Wow lets take a look" and Perl becomes a laughing stock when they all see it's just a patched Perl 5. What's worse this would jeopardise Perl 6, and all that's gone into it. I think a better title would have been "How to wipe Perl out for good with a simple version number change" or more simple "The Perl 7 one liner of death".

    Perl 6 is the future, an I firmly believe it'll fix everything. If people are impatient then the so…

  • Matt S Trout (mst) commented on Perl 7

    As an alternative idea - how about we pick a name rather than getting even further into the numbers game?

    See my blog post on the subject for my suggestion as to what to pick.

    -- mst, out

  • Ether commented on On the version number succeeding Perl 5

    I can see not wanting some warnings to be fatal, but it’s so rare to need to disable certain warnings entirely (e.g. numeric) that I’d be firmly on the side of keeping them enabled.

    Another change one could make in such a release is to do all the things tchrist lists as needed for full unicode and utf8 compliance:

  • adamlounds commented on How to write a test description

    Loving this test style.

    We're trying to follow a strict two-line format in the perl code, which makes the tests really easy to skim through.

    ok my $thing = Classname->new( %args ),
      "Can create a Classname";
    is $thing->accessor, $expected_value,
      "... and attribute was set ok";
    ok my $result = $thing->method_call,
      "... and can method_call";
    is $result, $expected_value,
      "... and method_call returned thing_we_wanted";

    /me is enjoying not creating tmpvars on their own lines all the time and having oodles of space to write test descriptions :-)

  • Aristotle commented on Perl 7

    Yes Jenda, these clearly look like dead projects to me. You’re talking out of your ass. As for your opinion that this supposed failure of the effort entitles you to give the people who are working on it a public “fuck you”, how about a nice big cup of shut-the-hell-up.

    Thank you.

Subscribe to feed Responses to Comments from

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 hosted by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.