Re^5: "use" modules inside modules

I've worked in environments (including the current one) whereby, entirely due to legacy reasons, cleaning up the code from a warning(s) POV, is not feasible with in the constraints of the project at hand - indeed, it would require a self-contained project to totally clean up the code.

The end result being that, wheresoever legacy code had/has to be used (pun intended) from within well-behaved code, it was/is done within a local block in order to circumvent the multifarious warnings that would otherwise be generated i.e.

{
    no warnings;
    use Legacy::Module;
}
[download]

The removal of the warnings from the legacy code can then be done in piece-meal fashion as a background task without compromising the aggressive timescales for the new code.

A user level that continues to overstate my experience :-))

Comment on Re^5: "use" modules inside modules Download Code

Replies are listed 'Best First'.
Re^6: "use" modules inside modules by bogaertb (Novice) on Jun 29, 2009 at 14:15 UTC
In this case it was not an issue. All perl scripts were run using -w. Changing that to include `use warnings 'all'` rather the using `#!/usr/bin/perl -w` did not result in more warnings neither at compile time nor at run-time (for me warnings are an indication of a possible coding error).	[reply] [d/l] [select]