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 calling .perl on callframe.my in Rakudo #2151
Comments
From @masak<moritz_> rakudo: say callframe().callframe(1).my.perl |
From @cokeOn Thu Sep 09 09:02:22 2010, masak wrote:
Output is now: -- |
The RT System itself - Status changed from 'new' to 'open' |
From @usev6This fails now with X::NYI and an adequate error message: $ perl6 -e 'say callframe().callframe(1).my.perl' I wonder whether this ticket could be closed now or how a proper test would look like. |
1 similar comment
From @usev6This fails now with X::NYI and an adequate error message: $ perl6 -e 'say callframe().callframe(1).my.perl' I wonder whether this ticket could be closed now or how a proper test would look like. |
From @zoffixznetTests: rakudo/rakudo@80cee36223 |
@zoffixznet - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#77754 (status was 'resolved')
Searchable as RT77754$
The text was updated successfully, but these errors were encountered: