in reply to Overriding methods and Inheritance

I don't quite understand why calling the version of funcB from your child class is bad. That's the expected behavior of overridden functions, and if I understand what you're doing correctly, it will just wrap the calls in multiple levels of eval.

I think you've discovered, though, at least one reason why this solution to your problem is extremely cumbersome. After all that work, would it have really been that hard to use evals in the original scripts that were using the exception throwing module in the first place?