Replies: 1 comment 1 reply
-
A typical way to get around this type of limitation is:
The choice is between preventing incorrectly initialized objects; and programming convenience in cases such as the one you describe. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I would like to create a c++ class with a
HighFive::File
attribute. This attribute is created in a different way depending on the options given by the user: it can be an hdf5 file with MPIOFileAccess property or each process opens its own hdf5 file.Unfortunately, it's not possible to do that because the default
File
constructor is protected. Could you explain why you made this choice?Thanks
Beta Was this translation helpful? Give feedback.
All reactions