in reply to Dealing with large chains of dependent packages

Yep, the real answer is to re-factor the package that pulls in half the other packages - that just doesn't sound right!

I think there are three approaches outside of re-factoring:

-derby
  • Comment on Re: Dealing with large chains of dependent packages

Replies are listed 'Best First'.
Re^2: Dealing with large chains of dependent packages
by techra (Pilgrim) on Aug 01, 2005 at 20:44 UTC
    Some caveats about SelfLoader. We've been using it in production here at my company for awhile and it has a few gotchas:

    1) Debugging becomes more difficult as line numbers aren't reperesnted correctly, nor the actual error. Often the error will be presented in the highest-up module used in your tree. I recommend having a script that will comment out the selfloader code while you are in development and put them back in when you are about to put things in production.

    2) Many editors get confused by SelfLoader because your actual subroutines sit below the __DATA__ declaration. I don't know how to trick Emacs or VI into seeing these correctly, but JEdit maintains its highlighting correctly.

    The speed gains in a non mod-perl environment are nice though.