https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67669
--- Comment #4 from Bernard <beyzman at gmail dot com> --- (In reply to Martin Sebor from comment #3) > I don't have access to a Windows machine and I can't confirm this on Linux, > but > I doubt the problem is due to GCC and suspect it's more likely due to some > bug/oddity in Windows and its newline handling (I did notice the "b" in the > call to fopen which should avoid these problems but still). Hi, I doubt that problem in Windows, because the same source compiled by Borland C++ Builder works well.
