5 ms·
This has nothing to do with binary versus text.
by metafunctor 4y ago
This has nothing to do with binary versus text.
- myself248 4y agoI think it does, insofaras OSs feel free to just fuck with the contents of files they think are text, replacing newlines willy-nilly. Files not identified as text are safe from such automatic tampering.
- MayeulC 4y agoI've never seen this behaviour at an OS level. This seems like an editor issue, and binary files are not exempt from being messed up by a slightly incompatible editor, far from it.
- nemetroid 4y agoPerhaps you have been spared from writing code for Windows: https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/fopen-wfopen?view=msvc-170 https://learn.microsoft.com/en-us/cpp/c-runtime-library/refe... > In text mode, carriage return-line feed (CRLF) combinations are translated into single line feed (LF) characters on input, and LF characters are translated to CRLF combinations on output.
- Dylan16807 4y agoIs there a reason I should blame the OS specifically and not the C runtime?
- nemetroid 4y agoI guess it depends on how specific you want to be. The Windows C runtime is a component of the OS.
- Dylan16807 4y agoWell you're not really supposed to use the OS copy of msvcrt.dll
- tedunangst 4y agoYes, library functions do what you ask them to do.