isocpp / isocpp/CppCoreGuidelines
error handling: any practice for library code?
Open
@BjarneStroustrup is already working on this.
Since Jun 20, 2019.
- Dominant language
- CSS
- Stars
- 45.3k
- Forks
- 5.6k
- PR merge metrics
- No merged PRs in 30d
Description
This is raised when some colleagues questioned if library code can use 1) exit, 2) abort, 3) throw exception techniques when something fatal happened.
One argues that for a library code, it shall not exit or abort, and possibly shall not throw exception. The application will do the check of return code and decide further error handling.
So question is, do we need some special care about writing library code when dealing with unrecoverable errors? and any reason behind that.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.