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
The same class-wide variable, accessed two different ways, behaves like two different variables in Rakudo #1478
Comments
From @masakThis be Rakudo db84bc on Parrot r43174. $ perl6 -e 'class A::B { my $c; method foo { $c = "OH HAI"; say $c } $ perl6 -e 'class A::B { my $c; method foo { $A::B::c = "OH HAI"; say Fair enough. So far Rakudo agrees with my expectations. But watch this: $ perl6 -e 'class A::B { my $c = 42; method foo { $A::B::c = "OH HAI"; $ perl6 -e 'class A::B { my $c = 42; method foo { $c = "OH HAI"; say Ok, so in the first case we set $A::B::c and $c is unaffected. I'd In the second case, we set $c and $A::B::c is unaffected. Furthermore, |
From @moritzOn Sun Jan 24 10:01:53 2010, masak wrote:
Now says Null PMC access in getprop() Not sure that's an improvement :-) |
The RT System itself - Status changed from 'new' to 'open' |
From @bbkrNOM: still broken bbkr:nom bbkr$ ./perl6 -e 'class A::B { my $c; method foo { $c = "OH bbkr:nom bbkr$ ./perl6 -e 'class A::B { my $c; method foo { $A::B::c = bbkr:nom bbkr$ ./perl6 -e 'class A::B { my $c = 42; method foo { |
From @masak<masak> r: class A::B { my $c = 42; method foo { $A::B::c = "OH HAI"; say The original ticket seems to stem from a confusion between my-scoped and |
@masak - Status changed from 'open' to 'rejected' |
Migrated from rt.perl.org#72326 (status was 'rejected')
Searchable as RT72326$
The text was updated successfully, but these errors were encountered: