{"id":86435,"date":"2020-06-25T01:42:12","date_gmt":"2020-06-24T23:42:12","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/anonsirovan-perl-7"},"modified":"2020-06-25T01:42:12","modified_gmt":"2020-06-24T23:42:12","slug":"anonsirovan-perl-7","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/anonsirovan-perl-7","title":{"rendered":"Perl 7 has been announced","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

At today's virtual conference for Perl language developers announced<\/a><\/noindex> the Perl 7 project, which will smoothly continue the development of the Perl 5 branch without radical changes. Perl 7 will be similar to the release Perl 5.32.0<\/a><\/noindex>, except for different default settings that better align with modern development practices. In all other respects, Perl 7 will remain the same Perl 5 and maintain compatibility with previously developed applications.<\/p>\n

A significant change in the version number will act as a marker for the transition to a new model of enhancing the functionality of the Perl language without noticeably breaking backward compatibility.
\nIt is expected that the creation of Perl 7 will help attract new developers to Perl and facilitate the process of adding significant new features to the language while maintaining compatibility with the existing codebase. The number 7 was chosen since Perl 6 was used in the development of the language, which is now is being developed<\/a><\/noindex> under the separate name Raku. The first release of Perl 7 is anticipated next year. The Perl 5.32 branch will be the last in the Perl 5 series and is planned to be supported for 5 to 10 years.<\/p>\n

The most notable change in Perl 7 will be the default inclusion of the mode \u201ctype manipulations,<\/a><\/noindex>\u201d, which implies strict checking of variable declarations, the use of symbolic references, and subroutine assignments. Using \u201cuse strict\u201d is considered good practice and is adopted by most developers. Similarly, it is planned to enable warning handling by default (\u201cuse warnings<\/a><\/noindex>«).<\/p>\n

In Perl 7, they also plan to stabilize and include by default some already existing experimental features such as function signatures<\/a><\/noindex> (\u201cuse feature \u2018signatures\u2019\u201d), allowing the specification of incoming arguments when defining a function and automating their count check (you will be able to write \u201csub foo ($left, $right) {\u201d instead of \u201csub foo { my($left, $right) = @_;}\u201d. Support for the \u201cisa\u201d operator will also be enabled by default for checking whether an object is an instance of a specified class or a derived class (\u201cif( $obj isa Package::Name )\u201d, as well as postfix dereferencing operations \u201c$sref->$*\u201d instead of \u201c${ $sref }\u201d, \u201c$aref->@*\u201d instead of \u201c@{ $aref }\u201d, and \u201c$href->%{ ... }\u201d instead of \u201c%$href{ ... }\u201d. <\/p>\n

The candidates for being disabled by default in Perl 7 are:<\/p>\n