You could look at Toolkit, which purports to eliminate company-specific boilerplate.
Personally, I'm not too happy with hiding "boilerplate" away, but if you have a strong company policy, using something like Toolkit might make it easier to do the right thing for everybody by implicitly loading the modules.
sitecustomize.pl is close, but it is run in its own scope so use strict; would not be enabled by this. Maybe consider adapting what common::sense does to your own needs? common::sense does its thing via XS, which is likely too unwieldly for your needs.
Modern::Perl does the following:
sub import { my ($class, $date) = @_; $date = $wanted_date unless defined $date; my $feature_tag = validate_date( $date ); undef $wanted_date; warnings->import; strict->import; feature->import( $feature_tag ); mro::set_mro( scalar caller(), 'c3' ); }
... and most likely, you could write Modern::Perl::MyCompany, which does the same, except with the modules you want, like by adding:
POSIX->import( 'strftime' );
In reply to Re: How to export several modules intu users name space to not have a use ...; use ...; use ...; with the same modules all over again
by Corion
in thread How to export several modules intu users name space to not have a use ...; use ...; use ...; with the same modules all over again
by bigj
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |