NOIRLAB: changes in unix/os/zfiotx #454
Open
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.
These are two commits extracted from NOIRLAB:
dcba136 fixed 'var might be clobbered by longjmp' warning on linux
I can't reproduce the warning on Linux; however the right solution here would not be declaring a
static CHAR *abuf, but instead having avolatile XCHAR *opTherefore, the original commit is replaced with this one.Also, as
tty_getrawis set in (possibly asynchronuous) signal handlers, it must be declared asstatic volatile sig_atomic_t tty_getraw.cd4dc30, bdfd8e7 catch/ignore EBADF when closing fd on background jobs (Mac)
These commits look overly complicated.
Why not just
Also, Just ignoring an error for
EBADFseems not thre right solution - why does EBADF appear in background jobs?Independent of this, there is a use of fcancel(fp), which is similar to what is in
zxwhen.c. There, it was replaced in #366 with something more portable; maybe we should re-use it here (moved toosproto.h?).Pinging @mjfitzpatrick for a potential discussion.