Christian,
Thanks for the report.
This looks like a memoization bug, in which a perltidyrc file is parsed
just once as a speedup. Until it is fixed, the workaround is to add the
flag '-nmem' either to your perltidyrc or to the argv list.
Steve
On Wed, Oct 15, 2014 at 11:10 AM, Christian Walde via RT <
bug-Perl-Tidy@rt.cpan.org> wrote:
Show quoted text> Wed Oct 15 14:10:10 2014: Request 99514 was acted upon.
> Transaction: Ticket created by MITHALDU
> Queue: Perl-Tidy
> Subject: Running perltidy twice in the same process on Windows with a
> custom ~/.perltidyrc results in a crash
> Broken in: (no value)
> Severity: (no value)
> Owner: Nobody
> Requestors: MITHALDU@cpan.org
> Status: new
> Ticket <URL:
https://rt.cpan.org/Ticket/Display.html?id=99514 >
>
>
> My ~/.perltidyrc:
>
> --maximum-line-length=120
> --backup-and-modify-in-place
> --paren-tightness=0
> --output-line-ending=unix
> --indent-columns=4
>
> My OS is Windows 7, and the code to reproduce is:
>
> use Perl::Tidy;
> Perl::Tidy::perltidy(
> source => \"", destination => \( my $t ),
> argv => [ "--no-backup-and-modify-in-place", "--no-check-syntax",
> "--no-standard-output", "--no-warning-output", ]
> ) for 1 .. 2;
>
> The output i get, regardless of input to perltidy, is, on the second
> perltidy call:
>
> Unrecognized line ending '
> '; expecting one of: win dos unix mac
>
>
