Skip to content

Clean-up and document goto_trace.h/cpp [DOC-136] #4075

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

Merged
merged 6 commits into from
Feb 5, 2019

Conversation

romainbrenguier
Copy link
Contributor

@romainbrenguier romainbrenguier commented Feb 5, 2019

No functional changes: only removing unused code and documenting.

  • Each commit message has a non-empty body, explaining why the change was made.
  • [na] Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
  • [na] The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
  • [na] Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
  • [na] My commit message includes data points confirming performance improvements (if claimed).
  • My PR is restricted to a single feature or bugfix.
  • White-space or formatting changes outside the feature-related changed lines are in commits of their own.

goto-programs implementation should be language independent, so there is
no reason to include a mode field.
This is unused and doesn't bring much compared to the standard erase
function.
This is only an intermediary function used by show_goto_trace.
It shouldn't be exposed in the interface.
The second version of show_goto_trace was just calling the other one
with a default value for the last argument. We do now that explicitly
in the signature and remove the need for a second function.
/// Step of the trace of a GOTO program
///
/// A step is either:
/// - an assignement
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

assignment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
/// - an assignement
/// - an assignment

bool show_function_calls;
/// how original code in plain trace
Copy link
Member

@peterschrammel peterschrammel Feb 5, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Show
Maybe: in plain text trace

@romainbrenguier romainbrenguier force-pushed the doc/symex_trace branch 2 times, most recently from 20638d7 to 0c7e8d8 Compare February 5, 2019 10:09
Copy link

@edstenson edstenson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo

Copy link
Contributor

@allredj allredj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫
This PR failed Diffblue compatibility checks (cbmc commit: 20638d7).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/99755367
Status will be re-evaluated on next push.
Please contact @peterschrammel, @thk123, or @allredj for support.

Common spurious failures:

  • the cbmc commit has disappeared in the mean time (e.g. in a force-push)
  • the author is not in the list of contributors (e.g. first-time contributors).

The incompatibility may have been introduced by an earlier PR. In that case merging this
PR should be avoided unless it fixes the current incompatibility.

Copy link
Contributor

@allredj allredj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫
This PR failed Diffblue compatibility checks (cbmc commit: 0c7e8d8).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/99756516
Status will be re-evaluated on next push.
Please contact @peterschrammel, @thk123, or @allredj for support.

Common spurious failures:

  • the cbmc commit has disappeared in the mean time (e.g. in a force-push)
  • the author is not in the list of contributors (e.g. first-time contributors).

The incompatibility may have been introduced by an earlier PR. In that case merging this
PR should be avoided unless it fixes the current incompatibility.

Add documentation to the main classes, functions and methods when their
meaning is not obvious.
Doxygen comments should start with ///
Copy link
Contributor

@allredj allredj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✔️
Passed Diffblue compatibility checks (cbmc commit: b88944d).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/99764171

@romainbrenguier romainbrenguier merged commit d66ccf8 into diffblue:develop Feb 5, 2019
@romainbrenguier romainbrenguier deleted the doc/symex_trace branch February 5, 2019 13:54
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

Successfully merging this pull request may close these issues.

5 participants