debug consistency: fix unused-but-set-variable warning #360
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.
@donnaaboise reported the following unused-but-set-variable warning.
This PR replaces the call
SC_ASSERT (prev_rank < sb->rank);
byFCLAW_ASSERT (prev_rank < sb->rank);
so that prev_rank is set and used consistently in an FCLAW_ENABLE_DEBUG environment.I was not able to reproduce the compiler warning. Does this solve the warning, @donnaaboise?
There are a few more occurrences of P4EST_ASSERT and P4EST_ENABLE_DEBUG in fclaw2d_convenience.c, forestclaw2d.c,
fclaw2d_p4est.c and patches/clawpatch/fclaw_clawpatch_output_vtk.c. I could go ahead and replace them with their FCLAW counterpart in another commit, if this is okay with you @donnaaboise @cburstedde. Such a change would prevent issues caused by sc/p4est and forestclaw having different debug configurations.