Bug #115570 for Sub-Attributes: Fails with perls

Thu Jun 23 22:31:29 2016 ANDK [...] cpan.org - Ticket created

Subject:

Fails with perls < 5.18

As per subject. Best illustrated with the matrix: http://matrix.cpantesters.org/?dist=Sub-Attributes%200.01 Sample fail report: http://www.cpantesters.org/cpan/report/b0a2903c-376b-11e6-b0e5-a9ff5116cbd0 If this is intentional, it would be cool if you could declare your requirement. That way the FAILS are converted to UNKNOWNS. Details about how to do it are on this page: http://wiki.cpantesters.org/wiki/CPANAuthorNotes HTH&&Thanks,

Fri Jun 24 11:52:23 2016 $_ = 'spro^^*%*^6ut# [...] &$%*c>#!^!#&!pan.org'; y/a-z.@//cd; print - Correspondence added

On Thu Jun 23 22:31:29 2016, ANDK wrote: Show quoted text

> As per subject. Best illustrated with the matrix: > > http://matrix.cpantesters.org/?dist=Sub-Attributes%200.01 > > Sample fail report: > > http://www.cpantesters.org/cpan/report/b0a2903c-376b-11e6-b0e5- > a9ff5116cbd0 > > If this is intentional, it would be cool if you could declare your > requirement. That way the FAILS are converted to UNKNOWNS. Details > about how to do it are on this page: > http://wiki.cpantesters.org/wiki/CPANAuthorNotes > > HTH&&Thanks,

The problem is the use of unescaped literal :: in a double-quoted string: *{"$class::$subroutine"} = $coderef; I am surprised the behaviour changed in 5.18. That may not have been intentional. In any case, at least one of the colons needs to be escaped: *{"$class\::$subroutine"} = $coderef; *{"$class:\:$subroutine"} = $coderef; and then it works. (I usually use the latter, since it is more exotic, but still perfectly readable. :-)

Fri Jun 24 11:52:23 2016 The RT System itself - Status changed from 'new' to 'open'

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

On Fri Jun 24 11:52:23 2016, SPROUT wrote: Show quoted text

> The problem is the use of unescaped literal :: in a double-quoted > string: > > *{"$class::$subroutine"} = $coderef; > > I am surprised the behaviour changed in 5.18. That may not have been > intentional.

It seems it was not. I have reported the inadvertent change in behaviour at <https://rt.perl.org/Ticket/Display.html?id=128478>. Perl is now inconsistent in how it parses "$foo::$bar" and "$foo::@bar", so the behaviour may change back in 5.26. Hence it would be good to change to module to use a backslash. Show quoted text

> > In any case, at least one of the colons needs to be escaped: > > *{"$class\::$subroutine"} = $coderef; > *{"$class:\:$subroutine"} = $coderef; > > and then it works. (I usually use the latter, since it is more > exotic, but still perfectly readable. :-)

Tue Jun 28 11:20:00 2016 DFARRELL [...] cpan.org - Correspondence added

Thanks for the responses everyone, very useful! This should be fixed per version 0.02

Tue Jun 28 11:20:10 2016 DFARRELL [...] cpan.org - Status changed from 'open' to 'resolved'

Tue Jun 28 11:20:10 2016 DFARRELL [...] cpan.org - Taken

Tue Jun 28 11:20:10 2016 DFARRELL [...] cpan.org - Fixed in 0.02 added

Bug #115570 for Sub-Attributes: Fails with perls < 5.18