Skip to content
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

BUG: Use GDCM as private dependency in ITKIOGDCM #1768

Conversation

blowekamp
Copy link
Member

@blowekamp blowekamp commented Apr 14, 2020

Make the third partly library a private dependency, for the ITK GDCM
ImageIO modules. This follows best practices of data encapsulation.

Move the implementation of the destructor to the cxx file as a best
practice as it ensure intonation of the vtable in the library.

PR Checklist

  • No API changes were made (or the changes have been approved)
  • No major design changes were made (or the changes have been approved)
  • Added test (or behavior not changed)
  • Updated API documentation (or API not changed)
  • Added license to new files (if any)
  • Added Python wrapping to new files (if any) as described in ITK Software Guide Section 9.5
  • Added ITK examples for all new major features (if any)

Refer to the ITK Software Guide for
further development details if necessary.

Make the third partly library a private dependency, for the ITK GDCM
ImageIO modules. This follows best practices of data encapsulation.

Move the implementation of the destructor to the cxx file as a best
practice as it ensure intonation of the vtable in the library.
@blowekamp blowekamp force-pushed the GDCMImageIORemoveUsePrivateGDCM branch from 1759484 to ca1913c Compare April 14, 2020 16:52
Copy link
Member

@thewtex thewtex left a comment

Choose a reason for hiding this comment

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

👍

@blowekamp blowekamp merged commit 91e897d into InsightSoftwareConsortium:master Apr 15, 2020
SimonRit pushed a commit to RTKConsortium/RTK that referenced this pull request Apr 15, 2020
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.

4 participants