[bug #43936] Completion of error handling

Follow-up Comment #8, bug #43936 (project make): I try to reduce return value ignorance a bit more. I find quick error detection generally better because immediate exception handling might also reduce the time during which the affected software will run under "unexpected" conditions. Should compu

[bug #43936] Completion of error handling

Follow-up Comment #7, bug #43936 (project make): I can only reiterate what I said before: I don't see any need for make to detect errors writing to stdout as early as possible. To be even more explicit: I don't see any need for make to detect errors writing to stdout at any time before the end of

[bug #43936] Completion of error handling

Follow-up Comment #6, bug #43936 (project make): I find that my question contained another bit of information for further considerations. How long does a program may continue to run after an error occurred? How do you think about to improve static source code analysis also for your software? http

[bug #43936] Completion of error handling

Follow-up Comment #5, bug #43936 (project make): I've already answered that question; re-asking it isn't going to change my answer. If you provide new information or insight, that might change it. ___ Reply to this item at:

[bug #43936] Completion of error handling

Follow-up Comment #4, bug #43936 (project make): I find a comment like the following unsafe. "… Besides, it's wasteful to check the return value from every call that writes to stdout …" Can the delay between error occurrence and exception handling by the function "close_stdout" become inap

[bug #43936] Completion of error handling

Follow-up Comment #3, bug #43936 (project make): I don't see any point in detecting errors writing to stdout as early as possible. If you can think of one please mention it. ___ Reply to this item at:

[bug #43936] Completion of error handling

Follow-up Comment #2, bug #43936 (project make): Would it be a bit safer to detect every error situation as early as possible? When does a failed output need an immediate reaction in this software? ___ Reply to this item at:

[bug #43936] Completion of error handling

Update of bug #43936 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Fixed Release:

[bug #43936] Completion of error handling

Follow-up Comment #1, bug #43936 (project make): putchar and puts are not handled purposefully: at the very end when make exits it will verify that there is no error with stdout. See the close_stdout() function in output.c file and the long comment before that: this is a standard method of handl

[bug #43936] Completion of error handling

URL: Summary: Completion of error handling Project: make Submitted by: elfring Submitted on: Mo 05 Jan 2015 10:10:58 CET Severity: 3 - Normal Item Group: Bug