History log of /external/clang/test/FixIt/fixit-unicode.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
bbe0175255d4da42cd99d93ca1e60c8eabcb4b9a 20-Jul-2012 Jordan Rose <jordan_rose@apple.com> Re-apply r160319 "Don't crash when emitting fixits following Unicode chars"

This time, make sure we don't try to print fixits with newline characters,
since they don't have a valid column width, and they don't look good anyway.

PR13417 (and originally <rdar://problem/11877454>)

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@160561 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/FixIt/fixit-unicode.c
43972898614d91c00982f10cdf7f2bfb4a9f6275 20-Jul-2012 Nico Weber <nicolasweber@gmx.de> Revert r160319, it caused PR13417. Add a test for PR13417.



git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@160542 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/FixIt/fixit-unicode.c
b04a45720ba0cbc4bdb08aebceefa184e22f8a93 17-Jul-2012 Jordan Rose <jordan_rose@apple.com> Weaken Unicode fixit test to work even if the character is printed escaped.

This should fix the failure on Windows.

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@160324 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/FixIt/fixit-unicode.c
ee07db7d91906d7ce371c972048e318901587933 16-Jul-2012 Ted Kremenek <kremenek@apple.com> This test appears to fail on win32.

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@160322 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/FixIt/fixit-unicode.c
6f977c3e7918f9a668164f3ce27f1baa9557eb82 16-Jul-2012 Jordan Rose <jordan_rose@apple.com> Don't crash when emitting fixits following Unicode characters.

This code is very sensitive to the difference between "columns" as printed
and "bytes" (SourceManager columns). All variables are now named explicitly
and our assumptions are (hopefully) documented as both comment and assertion.

Whether parseable fixits should use byte offsets or Unicode character counts
is pending discussion on the mailing list; currently the implementation uses
bytes (and has no problems on lines containing multibyte characters).
This has been added to the user manual.

<rdar://problem/11877454>

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@160319 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/FixIt/fixit-unicode.c
c7bd9fbecd50c1fcdc1092e37023dbb8677d4eed 12-Jul-2012 Benjamin Kramer <benny.kra@googlemail.com> Be lax about trailing whitespace when checking fixit formatting, this depends on locale settings.

If a non-unicode locale is used, the unicode character is escaped and any
byte that is in the escaped representation but not the semicolon will
become whitespace.

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@160113 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/FixIt/fixit-unicode.c
af082c3b163397c040c3a98c7a5f09ee2a0badef 12-Jul-2012 Benjamin Kramer <benny.kra@googlemail.com> PR13312: Don't crash when printing a fixit that ends in a unicode character.

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@160112 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/FixIt/fixit-unicode.c