> Date: Sat, 8 Oct 2022 21:23:53 -0700 > Cc: bug-make@gnu.org > From: Paul Eggert <egg...@cs.ucla.edu> > > On 2022-10-08 21:19, Eli Zaretskii wrote: > > I meant the "b" part, not the "+" part. On systems where that changes > > the bytestream written to the file, the change might require a > > suitable change where we read that stuff. > > If I understand things correctly the code was formerly using tmpfile > which does use "b", so I figured "b" was fine.
Ah, okay. Then I guess there's no problem after all. > Another way to think about it: GNU 'make' just writes text to the file. > On MS-Windows if you're writing text using "b" doesn't a later read by > another process work regardless of whether the read uses "b"? If the difference is only in EOL format, yes. But "b" has other implications, such as reading beyond the first ^Z byte. Although I doubt that this could happen in this case.
