I agree that my approach burns the users who execute my scripts, should somebody on my team create a Symbol.pm... However, what (I think) my approach avoids is the case that:
My boilerplate approach only hurts invocations of my scripts; the PERL5LIB approach hurts invocations of all scripts. Potentially.
I do like the idea of using a team-specific namespace... That seems clean, and enables me to leverage PERL5LIB. Thanks!
In reply to Re^4: layout/configuration of deployed files
by klassa
in thread layout/configuration of deployed files
by klassa
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |