From 0d78aae5df7fb17532f2d47869d16e836468fe3c Mon Sep 17 00:00:00 2001 From: Niels Dekker Date: Wed, 6 Nov 2024 15:20:51 +0100 Subject: [PATCH] DOC: Note in Migration Guide that PointSet::Clone() now copies its data - Addressed a comment by Matt McCormick at https://github.com/InsightSoftwareConsortium/ITK/pull/4923#issuecomment-2457473255 --- .../docs/migration_guides/itk_6_migration_guide.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/Documentation/docs/migration_guides/itk_6_migration_guide.md b/Documentation/docs/migration_guides/itk_6_migration_guide.md index 83e6588c3f2..fbc47e17cde 100644 --- a/Documentation/docs/migration_guides/itk_6_migration_guide.md +++ b/Documentation/docs/migration_guides/itk_6_migration_guide.md @@ -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.)