A simple use might look the following:

  package MyClass;
  use Class::MixinFactory -hasafactory;
  sub new { ... }
  sub foo { return "Foo Bar" }

  package MyClass::Logging;
  sub foo { warn "Calling foo"; (shift)->NEXT('foo', @_) }

  package MyClass::UpperCase;
  sub foo { uc( (shift)->NEXT('foo', @_) ) }

  package main;

  my $class = MyClass->class( 'Logging', 'UpperCase' );
  print $class->new()->foo(); 
  # Calls MyClass::Logging::foo, MyClass::UpperCase::foo, MyClass::foo
[download]

I've posted a draft of the documentation online.

• The ReadMe draws from my earlier posts to describe the motivation for this approach.
• The top-level Class::MixinFactory package includes the general usage instructions.
• The generation of new classes is done by instances or subclasses of Class::MixinFactory::Factory class, or base classes can inherit a delegation method from the Class::MixinFactory::HasAFactory class.
• Behind the scenes, the factory class generates its accessors with an inside-out method maker.
• Method redispatch is provided by a NEXT method that is similar to Damian Conway's NEXT module, but doesn't use AUTOLOAD.

There are a number of related modules on CPAN, but none with quite the same mix of functionality:

• I've looked at mixin, Class::Mixin, and Spiffy, but they don't seem to have a configurable factory object or support run-time mixin selection.
• The Class::Mix and Class::Mutator modules do provide run-time class generation with multiple inheritance, but don't provide a configurable factory object or a redispatch technique.
• The Class::Factory module has a factory interface but doesn't support multiple inheritance.
• There are also a number of packages which are addressing a similar area of concern, but don't use mixins, including: Class::Role, Class::Roles, Class::Trait, and Aspect.

Feedback would be welcome; some of the questions I'm considering are:

• Does the package name seem appropriate?
• Does the public interface seem reasonable?
• Are there other modules out there that do this same thing?
• Does the documentation manage to explain why someone might want to do such a thing?