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
say EXPORT::ALL causes Null PMC access #3166
Comments
From dagurval@pvv.ntnu.no$ perl6
$ perl6 --version |
From @usev6As a status update: There is still a Null PMC access with Parrot and the errors with Moar and JVM don't look that good as well: $ perl6-p -e 'sub a is export { "a" }; say EXPORT::ALL' $ perl6-m -e 'sub a is export { "a" }; say EXPORT::ALL' $ perl6-j -e 'sub a is export { "a" }; say EXPORT::ALL' |
1 similar comment
From @usev6As a status update: There is still a Null PMC access with Parrot and the errors with Moar and JVM don't look that good as well: $ perl6-p -e 'sub a is export { "a" }; say EXPORT::ALL' $ perl6-m -e 'sub a is export { "a" }; say EXPORT::ALL' $ perl6-j -e 'sub a is export { "a" }; say EXPORT::ALL' |
@usev6 - Status changed from 'new' to 'open' |
From @FROGGSI have some sort of progress to report: $ perl6-m --ll-exception -e 'sub a is export { "foo" }; say &EXPORT::ALL::a()' So, it fails in a different way with this patch: I keep on working on it but I wanted to post this information here in case I forget. |
@FROGGS - Status changed from 'open' to 'resolved' |
From @FROGGSAccidently closed it. Ups. |
@FROGGS - Status changed from 'resolved' to 'open' |
From @FROGGSNow is the right time to close it :o) Patch: rakudo/rakudo@96b9a86548 |
@FROGGS - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#118501 (status was 'resolved')
Searchable as RT118501$
The text was updated successfully, but these errors were encountered: