Bug#742004: perltidy.LOG file left behind

[Russ Allbery]

Don Armstrong <don at donarmstrong.com> writes:
> On Tue, 18 Mar 2014, Russ Allbery wrote:

>> I looked into this further. The problem is that Perl::Tidy now always
>> attempts to create a log file in the current directory unless told to
>> create it elsewhere with the logfile parameter to its constructor.
>> (There doesn't seem to be a way to tell it not to create the thing,
>> although maybe you can point it to /dev/null.) Perl::Critic's policy
>> for running Perl::Tidy doesn't pass that parameter or provide any way
>> for the caller to pass it.

> I've now uploaded a new version of perltidy which should not have this
> problem.

Thank you!

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>