Skip Menu |

This queue is for tickets about the Perl-Tidy CPAN distribution.

Report information
The Basics
Id: 123492
Status: resolved
Priority: 0/
Queue: Perl-Tidy
People
Owner: Nobody in particular
Requestors: cweyl [...] maxmind.com
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Thu Nov 02 13:52:18 2017 cweyl [...] maxmind.com - Ticket created
Subject: perltidy fails to handle indented heredocs
Date: Thu, 2 Nov 2017 12:52:06 -0500
To: bug-Perl-Tidy [...] rt.cpan.org
From: Chris Weyl <cweyl [...] maxmind.com>
With v5.26, a new heredoc operator was introduced: <<~. perltidy does not seem to recognize this, resulting in some rather unfortunate errors; e.g. embedded SQL is parsed. I took a peek at the source, but I'm not entirely sure where to start to address this -- apologies for the patchless report :)
  Thu Nov 02 20:48:11 2017 s7078hancock [...] gmail.com - Correspondence added
Subject: Re: [rt.cpan.org #123492] perltidy fails to handle indented heredocs
Date: Thu, 2 Nov 2017 17:48:02 -0700
To: "bug-Perl-Tidy [...] rt.cpan.org" <bug-Perl-Tidy [...] rt.cpan.org>
From: Steven Hancock <s7078hancock [...] gmail.com>
Chris, Thanks for the report. I have written a tentative patch and will include it in the next release which should be in January. Steve On Thu, Nov 2, 2017 at 10:52 AM, Chris Weyl via RT < bug-Perl-Tidy@rt.cpan.org> wrote: Show quoted text
> Thu Nov 02 13:52:18 2017: Request 123492 was acted upon. > Transaction: Ticket created by cweyl@maxmind.com > Queue: Perl-Tidy > Subject: perltidy fails to handle indented heredocs > Broken in: (no value) > Severity: (no value) > Owner: Nobody > Requestors: cweyl@maxmind.com > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=123492 > > > > With v5.26, a new heredoc operator was introduced: <<~. perltidy does not > seem to recognize this, resulting in some rather unfortunate errors; e.g. > embedded SQL is parsed. > > I took a peek at the source, but I'm not entirely sure where to start to > address this -- apologies for the patchless report :) > >
  Thu Nov 02 20:48:12 2017 The RT System itself - Status changed from 'new' to 'open'
  Thu Dec 14 09:48:12 2017 perltidy [...] users.sourceforge.net - Correspondence added
This is fixed in version 20171214.
  Thu Dec 14 09:48:12 2017 perltidy [...] users.sourceforge.net - Status changed from 'open' to 'resolved'