Move FakePointerExpression out of ACSL AST & refactor pointer backtranslation #708
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following up on this discussion on #707:
BacktranslatedACSLValue
forBacktranslatedExpression
and a newFakePointer
record (which replacesFakePointerExpression
). The new supertypeBacktranslatedACSLValue
replacesBacktranslatedExpression
in the public interface of ACSL backtranslation.BacktranslatedExpression
a record.CACSL2BoogieBacktranslator
: refactor extraction and backtranslation of pointer structs. Handle pointer names (now represented by a (private) recordPointerVariable
) and pointer values separately.