Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Error handling #54

Open
frtru opened this issue Apr 9, 2017 · 0 comments
Open

Error handling #54

frtru opened this issue Apr 9, 2017 · 0 comments

Comments

@frtru
Copy link
Owner

frtru commented Apr 9, 2017

Useful references:
http://gamedev.stackexchange.com/questions/46424/try-catch-or-ifs-for-error-handling-in-c
http://bitsquid.blogspot.ca/2012/01/sensible-error-handling-part-1.html

  • Adopt an uniform method of handling errors (instead of returning bools at some places and 0xFFFFFFFF at other places...)
  • If keeping the 0xFFFFFFF, use UINT32_MAX instead
  • For shaders it might be a bigger problem if an error occurs, because the program will simply not work properly (in contrast with the textures which is not a big problem for the app itself if they fail)
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

1 participant