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

Null PMC access in Rakudo when running --target=parse on a file with a class declaration #1054

Closed
p6rt opened this issue Jun 12, 2009 · 5 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Jun 12, 2009

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

Searchable as RT66546$

@p6rt
Copy link
Author

p6rt commented Jun 12, 2009

From @masak

Rakudo e61569f has problems parsing class declarations​:

$ cat A.pm
class A {
}
$ perl6 --target=parse A.pm
Null PMC access in find_method()
in Main (src/gen_setting.pm​:0)

This is kinda strange, because it can produce later stages without a
problem. Probably a PCT bug.

@p6rt
Copy link
Author

p6rt commented Jun 12, 2009

From @pmichaud

On Fri Jun 12 01​:02​:31 2009, masak wrote​:

Rakudo e61569f has problems parsing class declarations​:

$ cat A.pm
class A {
}
$ perl6 --target=parse A.pm
Null PMC access in find_method()
in Main (src/gen_setting.pm​:0)

This is kinda strange, because it can produce later stages without a
problem. Probably a PCT bug.

I'm guessing the above fails because --target=prase doesn't make use of
any action methods, and Rakudo's parser really needs the action methods
in order to parse properly. (This will largely change when we become
more STD-like.)

Currently PCT chooses to not send the action grammar along as part of
--parse because it assumes you only want the parse tree (and that parse
tree generation will be independent of action methods). But I can see
places where that might not be the case, so perhaps PCT should always
send the action methods along as well. I'll have to think about it a bit.

Pm

@p6rt
Copy link
Author

p6rt commented Jun 12, 2009

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

@p6rt
Copy link
Author

p6rt commented Mar 9, 2010

From @moritz

works now; resolving without spectest because --target=parse is not specced.

@p6rt
Copy link
Author

p6rt commented Mar 9, 2010

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

@p6rt p6rt closed this as completed Mar 9, 2010
@p6rt p6rt added the Bug label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant