use Perl

• Is it a bug or a feature? (Score:1)

  by nxadm (8942)

  Not completely into Moose yet, but isn't a role the equivalent of a Java interface?

  In that case, the behaviour you describe has been implemented there as a intended feature: a regular class *implements* the interface.

  Additionally, a role seems to also have the function of an abstract class as well. In Java, overriding concrete methods is, again, a feature you want.

  If you don't want to override a method simply do not include a overloading method in the implementing class.

  It looks like a (sensible) design dec
  • Re: (Score:2)

    by Ovid (2709)

    Roles are far more than interfaces. I strongly recommend reading up on them to understand what they do. The protect (usually) against method collision and they provide a default implementation. If you want to use one like an interface, it's simple:

    package MyRole::DoesSomething;
    
    use Moose::Role;
    requires qw(
        save
        search
    );

    And now your classes (or some other role composed into said classes) must provide save and search methods.

    However, if you have this:

    package MyRole::DoesSomethi
    • Re: (Score:1)

      by chromatic (983)

      And the class using the role also has an 'is_deletable' method, than this potentially very important behavior is silently discarded.

      For a definition of "silently" which means "Code I explicitly wrote in my class itself", perhaps.

      What if you extracted all behavior into roles and composed them into classes? I think that would produce the desired results.
      • Re:Is it a bug or a feature? (Score:2)

        by Ovid (2709) on 2009.04.14 21:26 (#68124) Homepage Journal

        You know, I've considered that, but only to work around this issue. I don't want to extract behavior into roles unless I intend and need for that behavior to be shared.

        Reply to This

        Parent