-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Compile without exceptions? #908
Comments
I took another look through at what it would take to have a completely exception free build and while not trivial it has gotten a lot easier than it used to be as I've slowly shifted new code to support it. I think I might be able to toss up an exception free draft in the next week or two. A real world test use case could be helpful for completing that use case as well. |
…Update bundled HTTP library to remove the use of exceptions for error handling. All exceptions have been replaced with the error_codes used by the rest of the library either returned or as an output parameter. Documentation has been updated to note when this has happened. The main library interface has been updated to ensure that all functions that can throw are labeled as such and have a non-throwing overload. Nothing has been removed from the main library interface so anyone who uses exception handling with the main library is unaffected. These changes are being done in preparation for adding options to build WebSocket++ on platforms with exceptions disabled. references #438 #908
Going to close this as a duplicate in favor of #438. There have been some code updates towards this goal and some additional details over on that issue. |
Hi @zaphoyd! Sorry I didn't reply sooner. The real world case would be related to devices that require (or perform better with) no exceptions. That's fine to close. Excited to see the update! |
Hi @sourjon yes, sorry I wasn't clear, I am familiar with why one would want to disable exceptions, what would be useful is having someone who already had an environment or codebase that disabled exceptions to try the new code and report back whether it actually works. =) I can do some theoretical tests but it would be nice to have some real world integration testing to confirm. |
Hi @zaphoyd , Yep. I have such a codebase available. I can definitely let you know once the updates posted. |
…Update bundled HTTP library to remove the use of exceptions for error handling. All exceptions have been replaced with the error_codes used by the rest of the library either returned or as an output parameter. Documentation has been updated to note when this has happened. The main library interface has been updated to ensure that all functions that can throw are labeled as such and have a non-throwing overload. Nothing has been removed from the main library interface so anyone who uses exception handling with the main library is unaffected. These changes are being done in preparation for adding options to build WebSocket++ on platforms with exceptions disabled. references zaphoyd#438 zaphoyd#908
Hello,
I'm working on a system that requires the code to be exception free. I've seen a prior post asking about this (#438) but it didn't appear to be resolved. Is there a way to turn off exceptions without heavily modifying the library directly?
Thanks!
The text was updated successfully, but these errors were encountered: