-
Notifications
You must be signed in to change notification settings - Fork 50
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 #6
Comments
@elfring Hello, thanks for your suggestion, which I appreciate. Please can you be so kind to file a formal PR (pull request) with a working(!) and tested(!) code, which can be added to the present methods. |
I suggest to avoid ignorance of return values a bit more. Are you interested to apply aspect-oriented software development? |
@elfring you wrote
Yes, that was what I tried when porting this "piece" of software to OS/2 and DOS in 90ies - later I backported to Linux. The software was and is ugly (even the main author, Udi, agreed) and needs massive refactoring. So the underlying goal should be: keep it working (agrep can be compiled for many platforms, and we should not break this), but clean up messy things. Personally, I don't have any free resources to fix also these things, and would be happy, if I can avoid all compiler warnings (there are so many, I tried to fix the "missing function prototype" issues, but could not even fix all of them) @elfring perhaps you can starting working and helping me here: try to help to bring the compiler warnings to an absolute mininum. |
Can a tool like "Artistic Style" help here? How do you think about to improve static source code analysis also for your software? Do you find information sources like the following useful?
|
I have looked at a few source files for your current software. I have noticed that some checks for return codes are missing.
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: