Re^3: Rename a Moo constructor from "new" to "run"

[karlgoethebier]

Thanks. But are you sure? Just because i still can't test it. I vaguely remember that it only worked with the SUPER::. Best regards, Karl

[tobyink]

use v5.16;

package Foo {
    use Moo;
    has blah => (is => 'ro', required => 1);
    sub run { shift->new(@_) }
}

say Foo->run(blah => 42)->blah;

Doing SUPER::new will probably work in this case, though if you call it repeatedly, you won't benefit from some of the optimizations Moo does. (Moo doesn't actually built a Foo::new sub straight away, but when Moo::new gets called, it will notice that Foo::new is missing, build an optimized constructor, install it, and goto it.)

In cases where you weren't using a class building toolkit like Moo, and Foo::new was a hand-written constructor, then you definitely wouldn't want to call SUPER::new because you'd be bypassing the class's hand-written constructor (in favour of the superclass's constructor) which might be doing important stuff.

[karlgoethebier]

Pretty cool. Best regards, Karl

[bliako]

SUPER::new() calls new() of parent-class, if any.

[choroba]

So does $self Class->new if no sub new was declared in the Class.

[bliako]

Omitting the pedantic: "Does $self->new make sense?", does Perl have something similar to new XYZ; which will search for the nearest new() all the way up the inheritance tree of XYZ?

5' Edit: perhaps Moo supplies these

[karlgoethebier]

Sure. That's why i did it in the example mentioned: Inheriting the constructor, renaming it and changing it's behavior. A plugin...