Skip to content

Commit

Permalink
DOC: Note in Migration Guide that PointSet::Clone() now copies its data
Browse files Browse the repository at this point in the history
- Addressed a comment by Matt McCormick at InsightSoftwareConsortium#4923 (comment)
  • Loading branch information
N-Dekker committed Nov 6, 2024
1 parent 35bbc1d commit 0d78aae
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions Documentation/docs/migration_guides/itk_6_migration_guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -97,3 +97,13 @@ Accessing outdated ITKv5 migration scripts
git worktree add .../ITKv5.4 v5.4.0
ls ../ITKv5/Utilities/ITKv5Preparation
```

Class changes
-------------

The `Clone()` member function of `itk::PointSet` now does a "deep copy" of its
data, creating a new instance that has a copy of the points, the point data and
the region information properties of the original PointSet object. With previous
ITK versions, `PointSet::Clone()` did not copy any data. (It previously just
created a default-constructed PointSet object, like `PointSet::CreateAnother()`
does.)

0 comments on commit 0d78aae

Please sign in to comment.