On 12/27/2013 07:35 AM, sri wrote:
Okay, so why intentional? Is there something inherently bad about
multiple inheritance or is it just a case of "don't need it so let's not
go there and muck with it"?
I've been a proponent of multiple inheritance in the past (with Catalyst),
but since changed my stance. The delegation pattern (used all over
Mojolicious) and roles simply lead to cleaner results.
+1. I can agree with that :)
On another note, I've been running into a rather odd problem since I
updated Mojolicious. I have a plugin, the plugin uses another module;
can't really show you code since it's proprietary stuff but it works
along the lines of:
Foo::Comp::Search is a simple little module that wraps around an
ElasticSearch and adds some common logic
Foo::Plugin::Search is a Mojolicious plugin that uses the component, and
instantiates a new one during registration and stuffs it in an app
attribute.
Since updating Mojolicious, this fails to compile, the error is a bit
baffling: "can't use 'Foo::Comp::Search' as a hashref ..." - it
originates in the "use" line that says "use Foo::Comp::Search".
Foo::Comp::Search on it's own has no problems, no syntax errors.
It worked fine for the people working on the project, it stopped working
for me, and stopped working for one other person, the only thing in
common was our respective updates to Mojolicious; is there anything in
the Plugin module that got changed recently that could explain this
behaviour? I've been looking at the commits on github but it's not
giving me any ideas :/ Hoping someone can shed light (even if it's "give
us more detail you numpty" :P)
--
You received this message because you are subscribed to the Google Groups
"Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/groups/opt_out.
