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
Proposal for enabling warnings with 'use v5.32' #17162
Comments
From @paliSpecifying 'use v5.12' or higher automatically calls 'use strict'. So what about automatically enabling also warnings when 'use v5.32' (or |
From @simcop2387I think the main concern with doing this would be that strict and the other Ryan Voots On Mon, Oct 7, 2019 at 5:36 AM (via RT) <perlbug-followup@perl.org> wrote:
|
The RT System itself - Status changed from 'new' to 'open' |
From @GrinnzOn Mon, Oct 7, 2019 at 5:04 PM Ryan Voots <simcop2387@simcop2387.info>
(Resent to list) I don't think that's a relevant concern. Some aspects of strict are -Dan |
From @paliOn Monday 07 October 2019 14:04:45 Ryan Voots via RT wrote:
No, some warnings are compile time and some warnings are runtime. Even Example of compile time warning:
Exactly. My proposed suggestion is backward compatible. It does not
|
From @paliAny comments from perl maintainers? Is this proposed change a good idea which could be integrated into Perl 5.32? |
From @jkeenanOn Mon, 14 Oct 2019 10:57:01 GMT, pali@cpan.org wrote:
I don't see a compelling argument for this. Simply saying that we should do something similar to what we did 10 years ago is not enough of a rationale. Nor do I see a groundswell of support for it. Thank you very much. -- |
From @karenetheridgeOn Mon, 14 Oct 2019 04:03:40 -0700, jkeenan wrote:
We're constantly reminding beginners to include 'use strict; use warnings;' at the top of every file, and we always reflexively add it ourselves, so is there a technical reason why we *shouldn't* add it to the 5.32 pragma? after all, it will only come into effect in new code (that can only run on 5.32 or later) so there is no worry about breaking old code, or surprising effects in cpan modules etc. |
From @iabynOn Mon, Oct 14, 2019 at 04:48:12PM -0700, Karen Etheridge via RT wrote:
But code can break on later versions of perl when new warnings are added. -- |
From @dur-randirOn Tue, 15 Oct 2019 03:13:55 -0700, davem wrote:
Can we than freeze 'use v5.xx', xx >= 32 to enable the exact warnings set that was in the xx version, and not 'warnings all' set? |
From wagnerc@plebeian.comI would not like to see warnings enabled by default with any use <version> statement. It would simply create new boilerplate for me and many others: "no warnings" in every script. Occasionally I do use warnings in development to make sure I haven't done something bonkers but then disable it. And frankly, many of the default warnings are pedantic. Thanks. |
From @paliOn Monday 14 October 2019 16:48:12 Karen Etheridge via RT wrote:
That is the reason why I proposed this change and opened discussion for |
Under the current proposal to have a new perl 7 that defaults to turning on |
The "Perl 7" plan has been raised once again. I really think we should look into this a second time. https://www.nntp.perl.org/group/perl.perl5.porters/2021/03/msg259374.html |
Migrated from rt.perl.org#134484 (status was 'open')
Searchable as RT134484$
The text was updated successfully, but these errors were encountered: