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

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.
  • Reading the Synopsis and the role conflict spectest [pugscode.org] doesn't suggest anything other than resolving it yourself:

    class PracticalJoke does Bomb does Spouse {
        method fuse() {
            return self.Bomb::fuse();
        }
        method explode() {
            return self.Spouse::explode();
        }
    }

  • Before Moose, Perl6 was the great hope to fix a lot of the ugliness with Perl's OO. Perl 6 was like Perl 5 but more. However with all the community effort going into Moose and related MooseX stuff, I'm concerned that a lot of the great ideas in Perl6 are going to always remain too fair behind. It's starting to seem like Perl6 is like Perl5 but different. I wonder if there's some way to increase the communication between the Moose group and the people doing OO Perl6 stuff. There's a lot of little things
    --
    Waiting on the Road to Eventually, I lost my Place On Line
    • Perl 5 is pluggable, and Moose is a great "external" improvement.

      Perl 6 is (in the realm of object orientation without question) even better and more pluggable than Perl 5, and you wonder that the default isn't is as good isn't as good as Perl 5 with a bunch of the best modules available?

      I think thats an understandable position, but don't forget that Perl 6 leaves room for improvement. It shouldn't be all that hard to write a module that allows additional syntax like

      class Foo does SomeRole :except<metho