Or you could use multiple inheritance: e.g. our @ISA=qw(A B). Is there a reason that you are using Mixin instead of multiple inheritance or did it just happen that way?

I don't generally recommend multiple inheritance because weird things can happen if method names aren't orthogonal and you try to get one class hierarchy to define methods that override same named methods in another class hierarchy (e.g. the "diamond inheritance problem"). However, in your case method name clashes doesn't seem to be an issue as you have no concerns importing them into your namespace. If subroutine syntax is an alternative then I would presume your mixin classes are flat as well.

Best, beth