Skip Menu |

This queue is for tickets about the Perlmazing CPAN distribution.

Report information
The Basics
Id: 124320
Status: resolved
Priority: 0/
Queue: Perlmazing

People
Owner: Nobody in particular
Requestors: 'spro^^*%*^6ut# [...] &$%*c
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in:
  • 1.2810
  • 1.2812
Fixed in: (no value)



Subject: Enabling latest feature bundle causes bleadperl breakage
The whole point of feature bundles is to allow perl to change things without breaking existing code. By unconditionally enabling the latest feature bundle, you are defeating the whole purpose of feature bundles. Your module happens to fail under ‘use v5.27’ because ^= is now strictly a numeric operator, ^.= being the string equivalent. The attached patch gets the tests working under bleadperl, but I think you should reconsider your approach to feature bundles.
Subject: open_l6RWnjCu.txt
diff -rup Perlmazing-1.2812-jfktWP/lib/Perlmazing/Perlmazing/get_aes_cipher.pm Perlmazing-1.2812-0/lib/Perlmazing/Perlmazing/get_aes_cipher.pm --- Perlmazing-1.2812-jfktWP/lib/Perlmazing/Perlmazing/get_aes_cipher.pm 2018-02-02 18:53:33.000000000 -0800 +++ Perlmazing-1.2812-0/lib/Perlmazing/Perlmazing/get_aes_cipher.pm 2018-02-04 12:32:59.000000000 -0800 @@ -1,4 +1,5 @@ use Perlmazing; +no if "$]" >= 5.027, feature => 'bitwise'; use Crypt::Rijndael; # Mainly ripped from Crypt::Rijndael::MySQL
Thank you so much for this report. I'll analyze the best approach to this ASAP. Francisco On Sun Feb 04 15:42:18 2018, SPROUT wrote: Show quoted text
> The whole point of feature bundles is to allow perl to change things > without breaking existing code. By unconditionally enabling the > latest feature bundle, you are defeating the whole purpose of feature > bundles. > > Your module happens to fail under ‘use v5.27’ because ^= is now > strictly a numeric operator, ^.= being the string equivalent. > > The attached patch gets the tests working under bleadperl, but I think > you should reconsider your approach to feature bundles.