use Perl

• SOTA (Score:1)

  by chromatic (983)

  I looked around on CPAN for what the state of the art in mixing is...

  The state of the art of mixins in Perl 5 is Class::Trait [cpan.org].
  • Re: (Score:1)

    by Aristotle (5147)

    Class::Trait [cpan.org] ++
• mixins versus traits (Score:2)

  by Ovid (2709)

  So you want to mixin your bomb class and your girlfriend class to your current class:

  package Bomb;
  
  sub fuse    { ... }
  sub explode { ... }
  
  package Girlfriend;
  
  sub fuse    { ... }
  sub explode { ... }

  What happens when you want the Bomb::fuse method (because you can control the timing) but you also want the Girlfriend::explode method (because it's presumably non-lethal)? Now you have an ordering problem and you can't eliminate it. Of course, you could just use delegation, but that does
• mixing in with SEx (Score:1)

  by rjbs (4671)

  I do most of my mixing in of methods with Sub::Exporter [cpan.org].
  
  I end up not often needing the override-and-super feature that I see as being the real benefit of mixin.pm -- but Sub::Exporter::Util::mixin_exporter can do that if I need it.

  --
  rjbs
• C3 heirarchy conversion woes (Score:1)

  by blblack (7766)

  Assuming that your diamondy inheritance heirarchy is somewhat sane, the most common problems that cause a hierarchy to be invalid are re-ordering of dependencies, which is relatively easy to spot and fix. Example: package A; our @ISA = qw/B C/; package B; our @ISA = qw/D E/; package C; our @ISA = qw/E D/; Because A inherits from B+C, and they each inherit D+E in a different order, C3 cannot resolve this. The fix is to use D+E in the same order in both places. Most issues converting legacy hierarchies
  • Re: (Score:2)

    by schwern (1528)

    
    "Assuming that your diamondy inheritance heirarchy is somewhat sane"
    

    
    I think I see the problem.