Perl Weekly
Issue #575 - 2022-08-01 - Backward compatibility
latest | archive | edited by Gabor Szabo
|
Hi there!
One of the ongoing discussions in the Perl community is the question of backward compatibility. One group of people say it is (one of) the most important traits of Perl that you can run very old code on a very new version of Perl. The other side mostly say that there are very few cases when this is actually needed and the change in the version of Perl is just one aspect of upgrades people need to handle.
Then comes the case, like the introduction of th $00 variable in Perl 5.32 that breaks the code of people who used that variable for their own purposes. This is not the first case where a change in perl (or for that matter in a CPAN module) breaks some working code. Neither will be the last.
So the question isn't IF there can be changes breaking backward compatibility, but how we deal with them? Do the authors give proper warning? Are there tools to find pieces of code that will be impacted? (e.g. a Perl Critic rule). Are there instructions how to fix the code that will be broken?
On the other side of the coin, how can a user - a user of Perl or a CPAN module - ensure that changes in any of the dependencies won't impact their product or service? How can they notice any impact before it reaches the production system? Possibly even before it reaches the development machines forcing the whole team to stop working.
Hint: write and run automated tests!
Enjoy your week!
Gabor Szabo
|
|
|
Articles
|
|
|
|
|
|
Web
|
|
CPAN
|
|
Perl 5
|
by Tom Wyant (WYANT)
Over on the p5p mailing list, a user raised the issue that use of variable $00 is an error starting with Perl 5.32, and asked that this "regression" be fixed.
|
|
|
The Weekly Challenge
The Weekly Challenge by Mohammad Anwar will help you step out of your comfort-zone. You can even win prize money of $50 Amazon voucher by participating in the weekly challenge. We pick one winner at the end of the month from among all of the contributors during the month. The monthly prize is kindly sponsored by Peter Sergeant of PerlCareers.
|
by Mohammad Sajid Anwar (MANWAR)
Welcome to a new week with a couple of fun tasks "Permuted Multiples" and "Reversible Numbers". If you are new to the weekly challenge then why not join us and have fun every week. For more information, please read the FAQ.
|
|
|
by Mohammad Sajid Anwar (MANWAR)
Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Last Sunday" and "Perfect Totient Numbers" tasks in Perl and Raku. You will find plenty of solutions to keep you busy.
|
|
|
by Adam Russell
Nice commentary about the blockers and also the solution. Great work, keep it up.
|
|
|
by Arne Sommer
Arne is one of the few veterans we have and he proved it this time by pointing that the "Last Sunday" task is very similar to the one in Week 13. Thank you for all your contributions.
|
|
by Colin Crain
Sweet and simple methodical approach. Short and sweet task analysis added too. Keep it up great work.
|
|
by Colin Crain
Loved the blog title, full mark for the creativity. You also get elaborate task analysis, you don't want to skip. Well done.
|
|
by James Smith
James always challenge us with his analytical and technical skill. I love reading his code. Thanks for sharing.
|
|
by Flavio Poletti (POLETTIX)
Raku version gets my vote this time. I simply loved it. Thank you for everything.
|
|
|
|
by Laurent Rosenfeld
Laurent made an extra effort and shared multiple solutions in Raku. Not only that we got solutions in 17 different languages as well. Great work.
|
|
by Luca Ferrari
Luca is known for his compact Raku solutions. This time too, we got two cool solutions in Raku. Thanks for sharing the knowledge with us.
|
|
by W Luis Mochan
Luis is showing his one-liner power once again. Apparently he can do anything in one-liner. Cool attempt.
|
|
by Peter Campbell Smith
Peter style of blogging is more like a discussion. It is always fun to follow his approach to each task. Keep it great work.
|
|
|
by Simon Green
Cool work on optimizing slow code to near perfect. Thanks for sharing the secrets. Well done.
|
|
by Stephen G Lynn
Are you serious? I find it hard to believe what I see. I have to check it again. I am impressed by the Last Sunday solution in Perl. Great work.
|
|
Rakudo
|
|
Weekly collections
|
|
|
Our client is looking for senior Perl developers, Node engineers, and those with mighty Python and SQL skills to lead their team. Cross-trained team members are their sweet spot, and whether you’re cross-trained yourself or are open to the possibility, this may be your perfect role.
|
|
This company is a global leader in machine intelligence, and they’re looking for a Natural Language Processing (NLP) whiz who has experience maintaining and improving large Perl applications and tooling ecosystems. From Finland to the Faroe Islands, this remote role is open to senior Perl developers who are within two hours of Amsterdam’s time zone.
|
|
Our international client provides online trading services. They’ve got a stack of projects that need the right Chief Software Architect to manage their team as they work through these projects, and that’s where you come in. Ideally, you are located in Malaysia. With offices in Malta or Dubai, these countries are also options. Not located in one of these three spots? We still want to hear from you,
|
|
Our client connects people in the UK and US seeking flatmates or homes to share. These flatmate matchmakers need a Software Developer (Backend) to increase the delivery capacity of their core team. Their core platform is mostly written in Perl, so Perl folks, this one’s for you. You’ll work with developers to create admin tools and implement and test new site features.
|
|
Our client has developed an online system that tracks, monitors, and manages a whole host of safety issues, including team member competency, asset management, and compliance checks. They’re keeping their clients safe one click at a time, and they want to add a Senior Fullstack Perl Developer to their team to help them do it.
|
|
You know, you could get the Perl Weekly right in your mailbox. Every Week. Free of charge!
|