-
Notifications
You must be signed in to change notification settings - Fork 577
use warnings FATAL => 'all' confuses parsing #14896
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
From @jimavThis is a bug report for perl from jim.avera@gmail.com, use warnings FATAL => 'all' I'm not complaining because Perl can't always pinpoint the #!/usr/bin/perl use warnings FATAL => 'all'; # confuses compiler sub f1(@); my $lots; sub f2(@); Flags: Site configuration information for perl 5.20.2: Configured by Debian Project at Tue Mar 3 11:42:20 UTC 2015. Summary of my perl5 (revision 5 version 20 subversion 2) configuration: Locally applied patches: @INC for perl 5.20.2: Environment for perl 5.20.2: |
From @maukeOn Thu Sep 10 15:29:01 2015, jim.avera@gmail.com wrote:
$ perl try.pl $ perl -v This is perl 5, version 22, subversion 0 (v5.22.0) built for i686-linux |
The RT System itself - Status changed from 'new' to 'open' |
From @jimavMy Perl is v5.20.2 and it says So it looks like the issue has already been fixed in v5.22.0 Thanks. |
From @khwilliamsonRejecting, as is already fixed as acknowledged by OP |
@khwilliamson - Status changed from 'open' to 'rejected' |
From @jimavThis is a bug report for perl from jim.avera@gmail.com, "use warnings FATAL => 'all'" immediately terminates the process For example, a mis-spelled variable name often causes subsequent, A solution might be to defer termination until after the end of compilation That way, all the usual diagnostics would be printed, so the user can see #!/usr/bin/perl $misspelled = 123; # sub myfunc(@) { } Flags: Site configuration information for perl 5.20.2: Configured by Debian Project at Thu May 14 17:30:11 UTC 2015. Summary of my perl5 (revision 5 version 20 subversion 2) configuration: Locally applied patches: @INC for perl 5.20.2: Environment for perl 5.20.2: |
From @jkeenanOn Tue Jan 19 13:40:48 2016, jim.avera@gmail.com wrote:
I strongly disagree with your request for a change in functionality. We already document why you should not be using "use warnings FATAL => 'all'" *at all*. From 'perldoc warnings' on perl-5.22.0: ##### I don't see any reason to encourage people -- implicitly or explicitly -- to use "use warnings 'FATAL => all'". Thank you very much. -- |
The RT System itself - Status changed from 'new' to 'open' |
From @jimavOn 01/19/2016 03:47 PM, James E Keenan via RT wrote:
I'm sorry you feel so strongly that you want to make FATAL extra FATAL is not depreciated, so I don't think refusing to make it more |
From @tonycozOn Mon Feb 08 23:06:11 2016, jim.avera@gmail.com wrote:
I don't know if Jim saw this in the ticket this was merged into, but: tony@mars:.../git/perl$ ./perl -Ilib ../127323.pl which changed in: commit 594b6fa treat fatal warnings after syntax errors as syntax errors Tony |
Migrated from rt.perl.org#126034 (status was 'rejected')
Searchable as RT126034$
The text was updated successfully, but these errors were encountered: