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 typing a variable as ::foo in Rakudo #1822
Comments
From @masak<diakopter> rakudo: my ::byte $a |
From @masak<diakopter> rakudo: my ::foo $x; say $x |
From @masak<jnthn> rakudo: my ::foo $x; |
@masak - Status changed from 'new' to 'open' |
From radu_cs85@yahoo.comAdded test in S04-declarations/my.t |
The RT System itself - Status changed from 'new' to 'open' |
From @kylehaThis is an automatically generated mail to inform you that tests are now available in t/spec/S04-declarations/my.t commit 1614779058b7c8f759221f1614ba3fab04992895 [t/spec] Added test for RT 72814 - Null PMC access when typing a my-declared variable as ::a in Rakudo. Inline Patchdiff --git a/t/spec/S04-declarations/my.t b/t/spec/S04-declarations/my.t
index 6f23c04..25145f7 100644
--- a/t/spec/S04-declarations/my.t
+++ b/t/spec/S04-declarations/my.t
@@ -1,7 +1,7 @@
use v6;
use Test;
-plan 62;
+plan 63;
#L<S04/The Relationship of Blocks and Declarations/"declarations, all
# lexically scoped declarations are visible">
@@ -247,4 +247,11 @@ eval_lives_ok 'my (%h?)', 'my (%h?) lives';
eval_lives_ok 'my $x = 3; class A { has .$y = $x; }; say A.new.y',
'global scoped variables are visible inside class definitions';
+#RT #72814
+
+{
+ #?rakudo skip 'RT 72814'
+ lives_ok {my ::a $a}, 'typing a my-declared variable as ::a works.';
+}
+
# vim: ft=perl6 |
From @bbkrNOM: mentioned test is already unfudged and passing |
@bbkr - Status changed from 'open' to 'resolved' |
From @cokeOn Wed Jun 09 14:45:50 2010, masak wrote:
Now they say: 00:19 < [Coke]> rakudo: my ::foo $x; say $x -- |
From @usev6The Null PMC access is gone, so I'm closing this ticket. The error message has changed slightly: $ perl6-m -e 'my ::foo $x; say $x' I added a test for this exception to S02-names-vars/names.t with commit Raku/roast@5e0641d092 If you don't think current behaviour is correct, please reopen the ticket. Also, there was another Ticket (#72814; with test in S04-declarations/my.t) about the Null PMC access with 'my ::foo $x;'. I'm gonna merge both tickets. |
1 similar comment
From @usev6The Null PMC access is gone, so I'm closing this ticket. The error message has changed slightly: $ perl6-m -e 'my ::foo $x; say $x' I added a test for this exception to S02-names-vars/names.t with commit Raku/roast@5e0641d092 If you don't think current behaviour is correct, please reopen the ticket. Also, there was another Ticket (#72814; with test in S04-declarations/my.t) about the Null PMC access with 'my ::foo $x;'. I'm gonna merge both tickets. |
@usev6 - Status changed from 'open' to 'resolved' |
From @cokeOn Tue Oct 28 14:41:35 2014, bartolin@gmx.de wrote:
This test now dies on the JVM with a java.lang.StackOverflowError re-opening ticket. |
@coke - Status changed from 'resolved' to 'open' |
From @usev6The test passes again (rakudo-j). I'm closing this ticket as resolved. |
1 similar comment
From @usev6The test passes again (rakudo-j). I'm closing this ticket as resolved. |
@usev6 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#75646 (status was 'resolved')
Searchable as RT75646$
The text was updated successfully, but these errors were encountered: