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.

Sign up for GitHub

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

Jump to bottom

error_code per operation complex the interface too much #2

Open

lichray opened this issue Oct 16, 2012 · 0 comments

lichray commented Oct 16, 2012

That does not feel good. But a 'traditional' global error code makes thread-safe coding hard.

My suggestions are:

Add an error_code member to directory_entry, *directory_iterator, and provide a member function like is_valid() for user to check the status;
Move the non-member operational functions into a context class, so that the error code can be managed in the same way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment