in reply to Code reuse and method sharing with OOP / CGI::Application

I've used #1 before and it works fine for things that are related to being a web controller. However, an OO purist would tell you that inheritance is not about sharing a bunch of random methods. I think your best bet is splitting the methods up into their more logical classes, especially if you eventually expect others to work on this code.
  • Comment on Re: Code reuse and method sharing with OOP / CGI::Application