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 handling #54

Open

frtru opened this issue Apr 9, 2017 · 0 comments

Labels

enhancement hacktoberfest task

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)

frtru added enhancement task labels

frtru added this to the Final draft of the CPU implementation milestone

frtru added the hacktoberfest label

frtru removed this from the Final draft of the CPU implementation milestone

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