{"id":104162,"date":"2022-05-26T21:37:04","date_gmt":"2022-05-26T19:37:04","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/perl-7-plavno-prodolzhit-razvitie-perl-5-bez-narusheniya-obratnoj-sovmestiosti"},"modified":"2022-05-26T21:37:04","modified_gmt":"2022-05-26T19:37:04","slug":"perl-7-plavno-prodolzhit-razvitie-perl-5-bez-narusheniya-obratnoj-sovmestiosti","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/perl-7-plavno-prodolzhit-razvitie-perl-5-bez-narusheniya-obratnoj-sovmestiosti","title":{"rendered":"Perl 7 will smoothly continue the development of Perl 5 without breaking backward compatibility.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The Perl Project Steering Committee summarized plans for the further development of the Perl 5 branch and the creation of the Perl 7 branch. During the discussions, the steering committee agreed that breaking compatibility with existing Perl 5 code is unacceptable, except in cases where incompatibility is necessary to address vulnerabilities. The committee also concluded that the language should evolve, and new features should be promoted more actively, simplifying access to emerging innovations and encouraging their adoption. <\/p>\n
Contrary to the original intentions that allowed breaking changes to be enabled by default in the Perl 7 branch, the new plan implies a gradual transformation of the Perl 5 branch into Perl 7 without breaking backward compatibility with existing code. The release of Perl 7.0 will not conceptually differ from the next Perl 5.xx branch. <\/p>\n
The development of new releases of Perl 5 will continue as before \u2014 new features added to the branch that are incompatible with old code will be included only when explicitly specified in the code with the pragma 'use version' or 'use feature feature'. For example, in version Perl 5.010, the new keyword 'say' was introduced, but since functions named 'say' could be used in existing code, support for the new keyword was enabled only by explicitly stating the pragma 'use feature 'say'. <\/p>\n
The new syntax added to the language, which previously resulted in an error when processed in earlier releases, will be available immediately without the need to specify special pragmas. For instance, in Perl 5.36, a simplified syntax for handling multiple values from a list at once ('foreach my ($key, $value) (%hash) {') will be available directly, even in code without the pragma 'use v5.36'. <\/p>\n
In its current form, in Perl 5.36, when using the pragma 'use v5.36', 13 incompatible features ('say', 'state', 'current_sub', 'fc', 'lexical_subs', 'signatures', 'isa', 'bareword_filehandles', 'bitwise', 'evalbytes', 'postderef_qq', 'unicode_eval', and 'unicode_strings') are activated by default, the 'use strict' and 'use warnings' modes are enabled, and support for the deprecated indirect object notation (where a space is used instead of '->') and multidimensional arrays and hashes in Perl 4 style ($hash{1, 2}) is disabled. <\/p>\n
When enough changes accumulate, instead of another release of Perl 5.x, a version Perl 7.0 will be formed, which will represent a snapshot of the state but will remain fully backward compatible with Perl 5. To include incompatible changes and settings, explicit addition of the pragma 'use v7' in the code will be required. That is, code with the pragma 'use v7' can be viewed as 'modern Perl', in which incompatible language changes are available, while without it \u2014 as 'conservative Perl', which will remain fully backward compatible with earlier releases. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"