Re: Auto-generated constructors not finding correct SUPER?

[simonm]

I ran into a vaugely-related problem with SUPER last year. (1, 2, 3)

If you want to avoid string evals, another approach might be to replace the use of SUPER with NEXT or Class::MixinFactory::NEXT. These perform a similar function, re-dispatching to superclass methods, but use other techniques to search the inheritance tree. As a result, they are slower than SUPER, but might work better in your situation.