Re^2: make test and File::Spec problems

Thank you. I had version 3.23 of Test::Harness and now updated to 3.25. Now it is working without warnings.

Is the warning now just suppressed from the new Test::Harness module or should I change something in the code to really solve the warning?

Comment on Re^2: make test and File::Spec problems

Replies are listed 'Best First'.
Re^3: make test and File::Spec problems by chromatic (Archbishop) on Jun 29, 2012 at 21:39 UTC
When earlier versions of `T::H` launched external Perl processes in which to run your tests, they unilaterally added the `-w` flag. That enables warnings globally throughout the entire Perl process, even if the author didn't develop with warnings enabled. Since the release of Perl 5.6.0 in early 2000, the warnings pragma has had lexical scoping, so that individual modules, files, and scopes can enable or disable warnings on their own. Something somewhere in File::Spec produces that warning, but no one who's patched that module has felt the need to fix it because it's clearly not an error and it only produces a warning if you ignore lexical warnings.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^3: make test and File::Spec problems
by chromatic (Archbishop) on Jun 29, 2012 at 21:39 UTC

When earlier versions of T::H launched external Perl processes in which to run your tests, they unilaterally added the -w flag. That enables warnings globally throughout the entire Perl process, even if the author didn't develop with warnings enabled.

Since the release of Perl 5.6.0 in early 2000, the warnings pragma has had lexical scoping, so that individual modules, files, and scopes can enable or disable warnings on their own.

Something somewhere in File::Spec produces that warning, but no one who's patched that module has felt the need to fix it because it's clearly not an error and it only produces a warning if you ignore lexical warnings.

[reply]
[d/l]
[select]