Hi Tux, progress marches on, like it or not ... Recently I found that the newest version of Devel::Declare breaks Method::Signatures, so I pinned my stack to Devel::Declare v0.006019. But that version does not compile with the new Perl 5.32.0 ...
(fwiw I know Devel::Declare is deprecated but I am a user, not the author, of Method::Signatures, which depends on it...)
The way forward always starts with a minimal test.
| [reply] |
Devel::Declare is deprecated for many good reasons. If you are using perl 5.32 (or indeed any version of perl later than 5.20.0), you can just use core signatures (perldoc.pl/signatures) instead.
-ether@cpan.org
| [reply] |
Hi Karen, thank you! But I think that's not quite a full picture.
Signatures have not lost the experimental tag in Perl 5.32. I recently asked dave_the_m what the sticking points were and he said that it remains undecided whether @_ will be populated or not. As I read the current doc, it is populated, so that would be an incompatible change.
In my work environment, as is true for many developers, it's not prudent to use experimental Perl features (because they change), so we don't do so.We're anxious to switch to native signatures, especially as Method::Signatures is getting more difficult to use, but we're not going to switch until we don't have to disable 'experimental' warnings.
The way forward always starts with a minimal test.
| [reply] [d/l] |
perl-5.32.0.tar.gz:
MD5: 7e12c2ef8f3fbf5ca615eecae222c4e3
SHA1: ddecb3117c016418b19ed3a8827e4b521b47d6bb
SHA256: efeb1ce1f10824190ad1cadbcccf6fdb8a5d37007d0100d2d9ae5f
+2b5900c0b4
update: https://www.cpan.org/src/5.0/
https://www.cpan.org/src/5.0/perl-5.32.0.tar.gz.sha256.txt | [reply] [d/l] |
| [reply] |
| [reply] |
Great, thanks syphilis!
I'll get it tested with berrybrew, which is something I haven't looked at in some time. I've got a couple of open issues submitted by users so it'll be a good time to ensure the new version is found and installs correctly.
I suppose I just didn't look deep enough, but usually I just peruse to their main page to check for updates.
| [reply] |