I read that and experimented enough to learn my mixin expectations from Ruby
didn't serve me :) But, in my pasted code, I only defined dispatch methods
for the mixins. Are you saying that the tuples can't be related by
inheritance at all?
Thanks,
Jim
On Wed, Dec 15, 2010 at 5:53 PM, Joe Groff <arc...@gmail.com> wrote:
> On Dec 16, 2010, at 6:52 AM, Jim mack wrote:
>
> > Teaser: 4 tuple 'brothers' each have distinct mixin. Mixins have generic
> words. Tuples do not have any generic words defined. Out of six calls
> through tuples, two trigger the wrong mixin.
>
> Inheritance and mixin dispatch don't mix. Try using a pure mixin hierarchy
> instead to get the behavior you expect—make a mixin hierarchy mirroring your
> tuple hierarchy, and have the child mixin classes be members of the parent
> mixin classes.
>
> -Joe
>
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d
> _______________________________________________
> Factor-talk mailing list
> Factor-talk@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/factor-talk
>
--
Jim
"I'm for extending the working Medicare program for our seniors all the way
back to contraception, so Americans can concentrate on living their lives
without fear of changing a job, going bankrupt from deductibles or fighting
HMO bureaucracy."
------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
