in reply to Re: Class Inheritance Abuse. Best way to fix it?
in thread Class Inheritance Abuse. Best way to fix it?

Hopefully he doesn't use BLL::OtherPackage elsewhere, and hopefully he'll remember to re-edit if he installs a new version.

Not that I have a better idea right now. :-(

  • Comment on Re^2: Class Inheritance Abuse. Best way to fix it?

Replies are listed 'Best First'.
Re^3: Class Inheritance Abuse. Best way to fix it?
by diotalevi (Canon) on Jun 05, 2006 at 21:45 UTC

    It doesn't matter if BLL::OtherPackage is used elsewhere. The exporting code runs as many times as is required. If you say use BLL::OtherPackage qw( ... ) then an import call will occur. Period. BLL::OtherPackage is only compiled once but that's ok because you shouldn't need to keep recompiling it.

    ⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊