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

If they're utility functions that aren't necessarily part of what the C::A module is for, there's no reason why you can't continue to put them in a module that uses Export. If they are merely "utility" and not parts of the C::A "object" nor part of their own objects, #3 makes perfectly clear sense, with the added advantage that you are already familiar with this tool.

  • Comment on Re: Code reuse and method sharing with OOP / CGI::Application