You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Activity
p-gen commentedon 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 commentedon 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 commentedon 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 commentedon Jul 29, 2023
💭 Would it matter if output redirection can occasionally fail?