Re^4: OO Pattern Container x Elements and Method Chaining

Thanks a lot, again.

my Moo(se)->skills are still limited

I don't think the overload is really necessary, I don't mind if two Wrapper::Elements identify differently

handles intrigues me, do you know how it's implemented?

Unfortunately we have a performance issue, too.

and

> # <- and any other Element methods.

means the delegated methods must be listed explicitly and updated when Element grows in methods? °

That's why I mentioned AUTOLOAD and/or inheritance in the OP.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery}

according to https://metacpan.org/pod/Moose#REGEXP I can dynamically filter all methods needed to be delegated at compiletime :)

Comment on Re^4: OO Pattern Container x Elements and Method Chaining Select or Download Code

Replies are listed 'Best First'.
Re^5: OO Pattern Container x Elements and Method Chaining by choroba (Cardinal) on Oct 08, 2021 at 18:04 UTC
> according to https://metacpan.org/pod/Moose#REGEXP I can dynamically filter all methods needed to be delegated at compiletime :) That's a Mooseism not present in Moo. `map{substr$_->[0],$_->[1]\|\|0,1}[\\|\|{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^ARGV,3]`	[reply] [d/l]