Skip to content
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

If statements in modules produce a Null PMC access at runtime in Rakudo #818

Closed
p6rt opened this issue Mar 22, 2009 · 5 comments
Closed

Comments

@p6rt
Copy link

p6rt commented Mar 22, 2009

Migrated from rt.perl.org#64072 (status was 'resolved')

Searchable as RT64072$

@p6rt
Copy link
Author

p6rt commented Mar 22, 2009

From @masak

<masak> rakudo​: module Foo { if 1 { say 42 } }
<p6eval> rakudo de786f​: OUTPUT«Null PMC access in
get_pmc_keyed()␤current instr.​: 'parrot;Foo;_block26' pc 129
(EVAL_20​:71)␤»
* masak submits

Other constructs, such as 'given' and different types of loops, behave the same.

@p6rt
Copy link
Author

p6rt commented Apr 28, 2009

From @jnthn

On Sun Mar 22 02​:15​:51 2009, masak wrote​:

<masak> rakudo​: module Foo { if 1 { say 42 } }
<p6eval> rakudo de786f​: OUTPUT«Null PMC access in
get_pmc_keyed()␤current instr.​: 'parrot;Foo;_block26' pc 129
(EVAL_20​:71)␤»
* masak submits

Other constructs, such as 'given' and different types of loops, behave
the same.

Fixed in git b105f4f, assigning to moritz++ for spectests.

Thanks,

Jonathan

@p6rt
Copy link
Author

p6rt commented Apr 28, 2009

The RT System itself - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented Apr 29, 2009

From @moritz

Tested in t/spec/integration/packages.t.

@p6rt
Copy link
Author

p6rt commented Apr 29, 2009

@moritz - Status changed from 'open' to 'resolved'

@p6rt p6rt closed this as completed Apr 29, 2009
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant