Bug #115526 for File-CodeSearch: Fails with bleadperl v5.25.1-193-g8e84dec

Tue Jun 21 23:01:23 2016 ANDK [...] cpan.org - Ticket created

Subject:

Fails with bleadperl v5.25.1-193-g8e84dec

As per subject. There is a new warning and it catches, IMO, a bug in Highlighter.pm. Sample fail report: http://www.cpantesters.org/cpan/report/c9f77224-35f8-11e6-974b-b539388fbd9d The warnings reveal that the variables $chars_front_tmp and $chars_back_tmp were negative in this context: https://metacpan.org/source/IVANWILLS/File-CodeSearch-v0.7.4/lib/File/CodeSearch/Highlighter.pm#L136 i.e. in: /\A (.{$chars_front_tmp}) /xms So the effect is the same as: % perl -le ' print "a" =~ /.{-1}/; ' which somehow works in all perls but now warns with bleadperl. HTH&&Thanks,

Wed Jun 22 00:34:25 2016 $_ = 'spro^^*%*^6ut# [...] &$%*c>#!^!#&!pan.org'; y/a-z.@//cd; print - Correspondence added

On Tue Jun 21 23:01:23 2016, ANDK wrote: Show quoted text

> As per subject. There is a new warning and it catches, IMO, a bug in > Highlighter.pm. Sample fail report: > > http://www.cpantesters.org/cpan/report/c9f77224-35f8-11e6-974b- > b539388fbd9d > > The warnings reveal that the variables $chars_front_tmp and > $chars_back_tmp were negative in this context: > > https://metacpan.org/source/IVANWILLS/File-CodeSearch- > v0.7.4/lib/File/CodeSearch/Highlighter.pm#L136 > > i.e. in: > > /\A (.{$chars_front_tmp}) /xms > > So the effect is the same as: > > % perl -le ' > print "a" =~ /.{-1}/; > ' > > which somehow works in all perls but now warns with bleadperl.

To clarify, {-1} currently matches the literal string "{-1}", which suggests that perhaps there is a bug in the module’s behaviour that the tests are not catching.

Wed Jun 22 00:34:25 2016 The RT System itself - Status changed from 'new' to 'open'