-
Notifications
You must be signed in to change notification settings - Fork 188
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
Completion of error handling #2
Comments
I'll take a handle for xtload() for fopen. Not too concerned with calloc or fopen for writes failing. |
I suggest to avoid ignorance of return values a bit more. |
A little overkill in my opinion |
I prefer a more complete error detection and exception handling. |
Okay, I'll pop in ecalloc() and efopen() wrappers |
assertations for callocs and fopens were added instead |
actually, now that I think about it, asserts can be disabled globally. efopen and ecalloc were added instead. |
Thanks for your small source code improvement. |
scanf you mean? I'll patch it |
Functions like fclose() and fprintf() will need also further software development attention, won't they? |
No, assuming that efopen() was successful, fclose() and fprintf() can be used without worry. |
Your assumptions are questionable in this case. There are additional failure possibilities to consider. How do you think about to improve static source code analysis also for your software? |
I rely on runtime analysis with valgrind. Static analysis is typically overkill at times. The metrics supplied by gcc's -Wall and -Wextra is usually enough. |
Would you like to extend the development methodology with any software tools? |
Developments done for the most part as this is a practice in minimalism, If you're looking for a fully developed neural net library then checkout FANN (https://github.com/libfann/fann). |
Would you like to add more error handling for return values from functions like the following?
The text was updated successfully, but these errors were encountered: