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
Null PMC access when modifying 'our'-variable declared outside of a class from inside the class in Rakudo #1327
Comments
From @masak<masak> rakudo: our $c; class T { $c++ }; T.new |
From @kylehaThis is an automatically generated mail to inform you that tests are now available in t/spec/S02-names/our.t commit 619cfa67371adeb61a8acba6cd17093b13acddf1 [t/spec] Test for RT #69460 Inline Patchdiff --git a/t/spec/S02-names/our.t b/t/spec/S02-names/our.t
index 4efa383..73309f3 100644
--- a/t/spec/S02-names/our.t
+++ b/t/spec/S02-names/our.t
@@ -1,7 +1,7 @@
use v6;
use Test;
-plan 7;
+plan 10;
# L<S02/Names/Symbols in the current package>
@@ -26,4 +26,16 @@ plan 7;
is OUR::c(), 'sub c', 'sub c called with OUR:: works';
}
+# RT #69460
+{
+ our $rt69460 = 1;
+ #?rakudo todo 'RT 69460'
+ eval_lives_ok 'class RT69460 { $rt69460++ }',
+ 'can compile a class that modifies our variable';
+ #?rakudo skip 'RT 69460'
+ ok T.new ~~ RT69460, 'can instantiate class that modifies our variable';
+ #?rakudo todo 'RT 69460'
+ is $rt69460, 2, 'class can modify our variable';
+}
+
# vim: ft=perl6 |
The RT System itself - Status changed from 'new' to 'open' |
From @masakOn Tue Sep 29 03:02:48 2009, masak wrote:
<masak> rakudo: our $c; class T { $c++ }; T.new; say $c |
@masak - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#69460 (status was 'resolved')
Searchable as RT69460$
The text was updated successfully, but these errors were encountered: