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

about the function return #2

Open
iHackerJi opened this issue May 21, 2022 · 2 comments
Open

about the function return #2

iHackerJi opened this issue May 21, 2022 · 2 comments

Comments

@iHackerJi
Copy link

When function error, why use the throw Exception the way?
why not return result Let's us to decide ,
when i not register the Exception Handler , my program will close ,not printf anything about the debug info

@HoShiMin
Copy link
Owner

I think that exceptions looks more natural here than statuses. What difficulties do you face when handling exceptions?

@iHackerJi
Copy link
Author

I think that exceptions looks more natural here than statuses. What difficulties do you face when handling exceptions?

no anything difficulties sir,i just want to say,use this way will let this library become strange,i can not easy to use it if the function error,i must be use try catch or register the exception handler Can only know the library function error

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