From: Pete B. <pb...@gm...> - 2010-12-07 20:08:11
|
On 2010.12.07 19:23, Pete Batard wrote: >> Why does that matter? GCC might handle CRLF line endings the way you >> want; many other tools you can use with C files (grep, for one) don't. > > Mmmm, I hadn't really considered that, even though I seem to recall that > Michael mentioned something like that. That's actually a good point. If > we expect people to use tools that can't handle CRLF in cygwin and > MinGW, then yes, I have to review my position. Just tested grep, more (less), vim, and a few other command line tools in cygwin and MinGW, and at least for the versions I have, they are CRLF aware. They will produce LF'd output however, so if we were to use grep to create a source, we'd get CRLF -> LF conversion that we might not want. I would still expect all the default cygwin/MinGW text tools to be CRLF aware (they run on Windows, so they'd better be), but unless we find concrete evidence that any text tool from these environments (and for all the versions we are planning to support) handles any line terminator, and that everybody who creates a text utility for cygwin/MinGW is also supposed to handle both terminators properly (which is a big if), we're running the risk of breakage. So the question is whether we consider that the possibility of people using text tools that can't handle CRLF properly in cygwin/MinGW outweighs the ability to move files around between environments. As I hadn't considered the former, and the discussion has been going long enough, I'll leave you guys decide on what you think should take precedence. Regards, /Pete |