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

V7_BCODE_DUMP broken #553

Open
joeedh opened this issue Apr 27, 2016 · 3 comments
Open

V7_BCODE_DUMP broken #553

joeedh opened this issue Apr 27, 2016 · 3 comments
Assignees

Comments

@joeedh
Copy link

joeedh commented Apr 27, 2016

Hi. V7_BCODE_DUMP is broken. The (recent?) addition of immediate strings to the bytecode format has made opcodes that use bcode_decode_lit (OP_PUSH_LIT, OP_SET_VAR, OP_GET_VAR, OP_SAFE_GET_VAR) ambiguous. This broke dump_op (which does not use bcode_decode_lit, and seems to just assume integer operands).

Thanks.

@dimonomid dimonomid self-assigned this May 6, 2016
@dimonomid
Copy link
Contributor

Yeah, sorry about that. We actually plan to implement it not as a compile-time option, but as a run-time flag. Hopefully will get it sorted in a few weeks.

@goniz
Copy link

goniz commented Jul 4, 2016

Any news on this issue?

@dimonomid
Copy link
Contributor

Sorry but not yet. We still struggle with other things which considered higher priority.

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

3 participants