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 "Ambiguous use of * resolved as operator *" warning #12905
Comments
From @nwc10I'm recording this bug mostly for completeness, not because I expect it to be $ perl -lwe '$* = \*STDERR; print $*foo' and the exit code is 0. Note that 3 of the 4 warnings from the parser are actually bogus, but the It's a regression introduced by 5.001 $ ~/Sandpit/5000/bin/perl -lwe '$* = \*STDERR; print $*foo' $ ~/Sandpit/5001/bin/perl -lwe '$* = \*STDERR; print $*foo' Nicholas Clark |
From @cpansproutOn Mon Apr 08 10:46:01 2013, nicholas wrote:
I can trigger the same bug without playing games with print’s indirect $ ./perl -Ilib -e 'foo**foo' This is basically the same as bug #76910. When the lexer parses a bareword, it looks at the previous character and The purpose of the code is to catch *bar *bar or &black &sheep. It’s one of these heuristics that is wrong too often (I’ve triggered the There may be other ways to trigger this (ticket’s) warning that I -- Father Chrysostomos |
The RT System itself - Status changed from 'new' to 'open' |
From @cpansproutOn Mon Jun 03 22:26:24 2013, sprout wrote:
Actually, the bogus message for ** and && could be fixed similarly to I wonder whether a variant of that could apply to $*foo.
-- Father Chrysostomos |
From @cpansproutOn Mon Apr 08 10:46:01 2013, nicholas wrote:
The ambiguity warning actually turns out to be very easy to fix. I have The ‘Bareword found where operator expected’ I have not touched, even Making even minuscule changes in that area is likely to break things $ ./perl -Ilib -MO=Deparse -e 'print $FOO + $x' So I think we should just leave it. -- Father Chrysostomos |
@cpansprout - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#117535 (status was 'resolved')
Searchable as RT117535$
The text was updated successfully, but these errors were encountered: