I would be reluctant to change anything, most-especially about a large number of modules that are now known to be working, and most-especially on your own volition e.g. just driven by some sense of aesthetics. Perl, AFAIK, does not have an #include facility. In any case, you are not only making a pervasive source-code change to many modules, but you are now coupling them one to another. Now, not only is the source-code instantly available to be seen, but identical code has been textually bound to all of them such that it can no longer be individually changed in any one of them. By whose authority was such a change made or contemplated?
I counsel that you should not make a change to a source-code file which does not have direct and necessary relevance to the problem being fixed and/or the feature being introduced by the associated work-order ticket. Did the change-review committee at your place of business create an order to make such a change and then give it to you? (I’m serious.) If they did not, then I would meekly continue to write my code exactly as it has always been written, “easier” or not.
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: How to export several modules intu users name space to not have a use ...; use ...; use ...; with the same modules all over again
by Anonymous Monk on Jan 12, 2015 at 16:13 UTC | |
by morgon (Priest) on Jan 12, 2015 at 17:37 UTC | |
by Your Mother (Archbishop) on Jan 12, 2015 at 17:41 UTC | |
|