This is a fix for Bug 6870.

On Windows, we really do want CRLFs to remain, otherwise the output
ends up looking incredibly bad when piped to a file (even though it
looks fine on the command prompt).  For instance:

clang.exe -E some_file.cpp > test.txt

With Unix line endings, that will produce output which appears all in
a single line in some text editors (such as notepad).  Such as:

#line 1 "some_file.cpp" #line 1 "some_file.cpp" #line 1 "<built-in>"
#line 1 "<built-in>" #line 138 "<built-in>" #line 1 "<command line>"
#line 1
and so on...

But with CRLFs, the output ends up looking fine:
#line 1 "some_file.cpp"
#line 1 "some_file.cpp"
#line 1 "<built-in>"
#line 1 "<built-in>"
#line 138 "<built-in>"
#line 1 "<command line>"
#line 1

~Aaron

Attachment: OptELineEndings.diff
Description: Binary data

_______________________________________________
cfe-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits

Reply via email to