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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Force a flush of the stdout buffer, ensuring that any buffered output is immediately written to the terminal without waiting for the buffer to fill or for the program to exit.
This resolves issue #526, which caused test failures due to output mismatches when executed in Lind.
This probably works as a quick fix. What happens if the fp gets changed from stdout? (like during dup) Does it change in libc as well?
I changed the logic. It now flushes only when stdout is not connected to a terminal device, avoiding unnecessary forced flush operations in interactive contexts and eliminating edge cases.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Force a flush of the
stdoutbuffer, ensuring that any buffered output is immediately written to the terminal without waiting for the buffer to fill or for the program to exit.This resolves issue #526, which caused test failures due to output mismatches when executed in Lind.
Results: