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
strict does not ban all barewords #16838
Comments
From wagnerc@plebeian.comUsing the strict pragma does not ban all usages of barewords or force Tested on Perl 5.22.4 and 5.29.8 Examples: $ perl -MO=Deparse,-p,-q,-x20,-P -e 'use strict; print "$^X $^V\n"; my Thanks. |
From @tonycozOn Mon, 04 Feb 2019 15:16:24 -0800, wagnerc@plebeian.com wrote:
split is fixed by my patch in #133822. sort specially allows for a bareword subname for the sort sub and dies at runtime if the sub named doesn't exist, even if the sub doesn't need to be called: $ ./perl -Ilib -e 'use strict; my @list; print sort FOO @list; ' Tony |
The RT System itself - Status changed from 'new' to 'open' |
From @GrinnzOn Mon, 04 Feb 2019 21:09:43 -0800, tonyc wrote:
Not entirely true. See #36333, #130178, #133138. -Dan |
From @GrinnzOn Tue, 05 Feb 2019 00:13:43 -0800, grinnz@gmail.com wrote:
Last one should be #133178 -Dan |
From wagnerc@plebeian.comThe behavior of sort() is especially aberrant. I found an even older ticket! https://rt-archive.perl.org/perl5/Ticket/Display.html?id=3629 This is surely the source of many sideways bugs. Why doesn't sort() require the & character to name a sorting subroutine just like every other grab of a subroutine? sort &foo @list; |
Migrated from rt.perl.org#133823 (status was 'open')
Searchable as RT133823$
The text was updated successfully, but these errors were encountered: