Slash Boxes
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 ]

Matts (1087)

  (email not shown publicly)

I work for MessageLabs [] in Toronto, ON, Canada. I write spam filters, MTA software, high performance network software, string matching algorithms, and other cool stuff mostly in Perl and C.

Journal of Matts (1087)

Thursday October 25, 2001
04:04 AM

Perl 6 for Damians

[ #1070 ]

Well, I've voiced my opinion on IRC, and I thought it was time to make it stand up on its own. So I wrote a rebuff to Pier's article. The rebuff isn't meant to be against Piers by any stretch, but against where I see Perl 6 going.

Note that the URL above won't be the final resting place, so don't link to it. The article is also in flux, as I'm accomodating feedback from people. So please use the comments facility here to respond.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • disclaimer: I like where perl6 is going, but I certainly respect your dislike of that direction. These comments are intended only to help you clarify your opinion, not to de-value your opinion.

            > a number of changes are being made for the
            > sake of change. Things that we use a _lot_
            > in Perl 5, like '.' for concatenating, and
            > the dereference operator are going to change

    The fa
    • OK, one thing that people have seemed to completely miss in my discussion of this is my fundamental objection: Perl 6 won't parse Perl 5.

      I accept a lot of your points and take them on board. My point about the file test operators wasn't that I dislike the new syntax - I think it's *much* better than doing tests on the magic underscore. I just dislike the file test operators altogether :-)

      You ask if I'd like to see slice and grep moved into a module. Well no, I wouldn't, because they are functions that o
      • Ah... I think I understand what you mean now. The reason that I can't just do

             sub assert_with_comparator {

        Is because I need the automatic currying behaviour, which comes from $^comparator, $^a & $^b ($^foo introduces a named currying parameter, in the same way as $^_)


            sub (&comparator, $a, $b) is curried {

        will become a valid way of declaring a cur