The stupid question is the question not asked | |
PerlMonks |
Re^7: Modernizing the Postmodern Language?by salva (Canon) |
on Jul 03, 2020 at 15:26 UTC ( [id://11118874]=note: print w/replies, xml ) | Need Help?? |
As someone who 'knows perl', adding a one line pragma to keep your wild and crazy weekend coding lifestyle intact is hardly an onerous task. But it is quite the contrary, it would be much easier for me to say no strict the very rare times I need it than use strict all the other times. The issue for me is breaking backward compatibility just for that, for so small gain. So, let me express it in a different way: you come to me saying we are going to break backward compatibility because ...
But instead, they are saying, we are just releasing perl 5.xx as perl 7, changing some defaults and so, my old code may become broken, the applications I wrote for my company may become broken, the modules we use from CPAN may become broken (and by the way, break my code and my company apps in some other ways). I would have to revisit my code, convince people to fix their modules on CPAN, or just apply for maintanership, or fork them, and keep then in our private ForkedPAN. Also, what is worse, as you are not adding a "use v7" in your perl 7 code, when in a couple of years perl 8 comes out, it is going to break some of it again, because it is going to apply the perl 8 semantics to perl 7 code. So, in summary, don't get me wrong, I sympathize with what the p5 porters are trying to do. I understand the limitations they are facing, the scarce man power they are, and that they want to announce to the world that perl is well alive. But I also think that they should be more ambitious. I would like perl 7 to be what we expected from perl 6 (instead of what it became): a new powerful language with the syntax of perl 5 (extended).
In Section
Meditations
|
|