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

Error interface improvements in C #303

Open
martukas opened this issue May 9, 2018 · 0 comments
Open

Error interface improvements in C #303

martukas opened this issue May 9, 2018 · 0 comments
Assignees

Comments

@martukas
Copy link
Collaborator

martukas commented May 9, 2018

Need to bring up the following with HDF group (observations from #300):

  1. If H5E_error2_t could be made to initialize its C-string pointers as null. Would help avoid the problem of exceptions while in the error handling block. We do need to transfer those strings to std::string. I don't think that's unreasonable.
  2. Getting messages for major and minor error numbers is itself prone to creating another error stack, in effect overwriting the existing one. This is as problem, because we do want to collect all the error information immediately, not at some later point. The way it is now is like shooting yourself in the foot.
  3. No way to determine the state of the error auto-printing mechanism in the C-API without producing more errors, again overwriting the error stack. Every time we generate an exception based on the C-API error stack we need to check this state. If it didn't work like this, we could avoid using the singleton.
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

No branches or pull requests

2 participants