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 :)
In reply to Re^4: OO Pattern Container x Elements and Method Chaining
by LanX
in thread OO Pattern Container x Elements and Method Chaining
by LanX
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |