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

Completion of error handling #3

Open
elfring opened this issue Dec 19, 2016 · 4 comments
Open

Completion of error handling #3

elfring opened this issue Dec 19, 2016 · 4 comments

Comments

@elfring
Copy link

elfring commented Dec 19, 2016

Would you like to add more error handling for return values from functions like the following?

@p-gen
Copy link
Owner

p-gen commented Dec 19, 2016

Can you be more precise? The "usage" function returns no value and the value returned by "parse_sed_like_string" is already tested.

@elfring
Copy link
Author

elfring commented Dec 20, 2016

I suggest to avoid ignorance of return values a bit more.
How do you think about to care also if a file output or a string copy really succeeded?

@markschuh
Copy link

markschuh commented Jul 29, 2023

Looks to me as this issue was resolved on same day - but the issue was not closed.

The return value for strdup are handled now with the changes in 768f82b
And ignoring the return value of *printf functions is usually not considered that a relevant issue - at least not, when this is done during output of help messages to stdout.

@elfring
Copy link
Author

elfring commented Jul 29, 2023

💭 Would it matter if output redirection can occasionally fail?

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

3 participants