Skip to content

Conversation

luke-jr
Copy link
Member

@luke-jr luke-jr commented Jul 3, 2017

When we last discussed making scripts debuggable (sometime after #3901), the plan was to instead trace execution rather than single-step through it.

This is a dependency step toward that, and is eventually used for the RPC verifyscript to parse its "flags" option.

See also #10729

@jonasschnelli
Copy link
Contributor

Needs rebase

@luke-jr
Copy link
Member Author

luke-jr commented Sep 2, 2017

Rebased

@laanwj
Copy link
Member

laanwj commented Sep 6, 2017

I'm okay with moving this out of the tests if it's necessary in another place, however the from/to string stuff doesn't belong with the interpreter consensus code IMO. Better to keep it in a separate compilation unit, like with the CBitcoinAddress split done in #11117.

@laanwj
Copy link
Member

laanwj commented Nov 20, 2017

@luke-jr ping?

@luke-jr
Copy link
Member Author

luke-jr commented Nov 20, 2017

Hmm, so where would you suggest? Bundle it in with RPC-specific stuff?

@luke-jr luke-jr force-pushed the scriptflag_strings branch from 97cae39 to e2e183b Compare April 1, 2018 07:05
@luke-jr
Copy link
Member Author

luke-jr commented Apr 1, 2018

Rebased, and moved it to script/script_flags.{h,cpp} for now.

@luke-jr
Copy link
Member Author

luke-jr commented Jun 16, 2018

Closing due to apparent lack of interest/reviewers

@luke-jr luke-jr closed this Jun 16, 2018
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Dec 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants