BUG: incorrect bitSet auto-vivify in snappy
- should use bitSet::set() and not bitSet::operator[] to auto-vivify out-of-range entries - use bitSet::test() instead of bitSet::operator[] when testing non-const variables - circumvents any potential out-of-range issues.
Showing
- src/mesh/snappyHexMesh/meshRefinement/meshRefinement.C 4 additions, 4 deletionssrc/mesh/snappyHexMesh/meshRefinement/meshRefinement.C
- src/mesh/snappyHexMesh/meshRefinement/meshRefinementBaffles.C 3 additions, 3 deletions...mesh/snappyHexMesh/meshRefinement/meshRefinementBaffles.C
- src/mesh/snappyHexMesh/meshRefinement/meshRefinementProblemCells.C 2 additions, 2 deletions...snappyHexMesh/meshRefinement/meshRefinementProblemCells.C
- src/mesh/snappyHexMesh/meshRefinement/meshRefinementRefine.C 1 addition, 1 deletionsrc/mesh/snappyHexMesh/meshRefinement/meshRefinementRefine.C
- src/mesh/snappyHexMesh/snappyHexMeshDriver/snappyLayerDriver.C 3 additions, 3 deletions...esh/snappyHexMesh/snappyHexMeshDriver/snappyLayerDriver.C
- src/mesh/snappyHexMesh/snappyHexMeshDriver/snappySnapDriver.C 3 additions, 3 deletions...mesh/snappyHexMesh/snappyHexMeshDriver/snappySnapDriver.C
- src/mesh/snappyHexMesh/snappyHexMeshDriver/snappySnapDriverFeature.C 9 additions, 9 deletions...appyHexMesh/snappyHexMeshDriver/snappySnapDriverFeature.C
- src/mesh/snappyHexMesh/trackedParticle/trackedParticle.H 3 additions, 4 deletionssrc/mesh/snappyHexMesh/trackedParticle/trackedParticle.H
Please register or sign in to comment