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
bogus "used only once" warnings #13309
Comments
From @maukeCreated by @mauke% perl -we 'sub A::f; BEGIN { 0 if *{"A::f"}{CODE} }' % perl -we 'sub A::f; BEGIN { 0 if *{"A::g"}{CODE} }' % perl -we 'BEGIN { 0 if *{"CORE::lc"}{CODE} }' % perl -we 'BEGIN { 0 if *{"CORE::eval"}{CODE} }' I don't think this code should trigger any "used only once" warnings. I'm Even so, why does *{"CORE::eval"} warn but not *{"CORE::lc"}? Perl Info
|
From zefram@fysh.orgl.mai@web.de wrote:
Because \&CORE::lc is a thing, but the behaviour of CORE::eval can't be -zefram |
The RT System itself - Status changed from 'new' to 'open' |
From perl@profvince.com
perl 5.14.4 also throws the warning. The difference appears with perl 5.16.
Here's the list of all of them : $ perl5.18.1 -MB::Keywords=@Functions -le'for (@Functions) { system |
From zefram@fysh.orgAs discussed, the warning is not bogus. This ticket should be closed. -zefram |
From @iabynOn Sat, Dec 16, 2017 at 04:00:51AM +0000, Zefram wrote:
Although \&CORE::eval returns an undef CV, as compared to \&CORE::lc which So its not clear to me why one should warn and the other shouldn't. -- |
From @cpansproutOn Mon, 18 Dec 2017 03:45:37 -0800, davem wrote:
$ perl5.26.0 -le 'print defined *{"CORE::lc"}||0; print defined ${"CORE::eval"}||0;' -- Father Chrysostomos |
Migrated from rt.perl.org#119991 (status was 'open')
Searchable as RT119991$
The text was updated successfully, but these errors were encountered: