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

Remove exception from normal execution path #159

Open
daravi opened this issue Nov 9, 2021 · 0 comments
Open

Remove exception from normal execution path #159

daravi opened this issue Nov 9, 2021 · 0 comments

Comments

@daravi
Copy link

daravi commented Nov 9, 2021

As it is, using boost::interprocess::open_or_create in the constructors can lead to exceptions that are internally caught. This makes debugging hard as I have to skip those exceptions until I get to an actual "exception". IMO an "exception" should only be thrown in exceptional circumstances and not during normal operation.

If possible please add a way check if a shared memory segment exists given the key without needing to throw an exception. I think this would also help with the usability of the library.

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

1 participant