develooper Front page | perl.perl5.porters | Postings from September 2018

Fatalizations promised for perl-5.30: what is their status

Thread Next
From:
James E Keenan
Date:
September 11, 2018 17:24
Subject:
Fatalizations promised for perl-5.30: what is their status
Message ID:
20180911172418.2385.qmail@lists-nntp.develooper.com
While investigating a question posed on #p5p today by pink_mist, I ran 
this code:

#####
(01:13:31 PM) kid51: $ ./perl -Ilib -v | head -2 | tail -1
(01:13:44 PM) kid51: This is perl 5, version 29, subversion 3 (v5.29.3 
(v5.29.2-48-g295a484ee2*)) built for x86_64-linux  (blead)
(01:13:53 PM) kid51: $ ./perl -Ilib -E 'my $xenu if 0;'
(01:14:01 PM) kid51: Deprecated use of my() in false conditional. This 
will be a fatal error in Perl 5.30 at -e line 1.
(01:14:21 PM) randir left the room (quit: Remote host closed the 
connection).
(01:14:47 PM) kid51: ^^ That version of this warning was added in early 
2017 by Abigail in c437f7ac8463f610ccc01a2df0ad2287742d3edd
(01:15:17 PM) kid51: However, it appears we haven't actually implemented 
the fatalization yet; otherwise, I would have gotten an exception
#####

This led me to wonder:  At this point in the 5.29->5.30 development 
cycle, have we implemented the 5.30 fatalizations we promised by adding 
"This will be a fatal error in Perl 5.30" during the 5.27->5.28 cycle?

It appears that at least in this case -- my() in false conditional -- we 
have not.

So that we can research all relevant cases, I'm attaching an ack of the 
core for the places where this warning appears.

Thank you very much.
Jim Keenan

Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About