summaryrefslogtreecommitdiffstats
path: root/clang/test/FixIt/fixit-unicode.c
Commit message (Collapse)AuthorAgeFilesLines
* Re-apply r160319 "Don't crash when emitting fixits following Unicode chars"Jordan Rose2012-07-201-1/+19
| | | | | | | | | 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>) llvm-svn: 160561
* Revert r160319, it caused PR13417. Add a test for PR13417.Nico Weber2012-07-201-19/+1
| | | | llvm-svn: 160542
* Weaken Unicode fixit test to work even if the character is printed escaped.Jordan Rose2012-07-161-4/+5
| | | | | | This should fix the failure on Windows. llvm-svn: 160324
* This test appears to fail on win32.Ted Kremenek2012-07-161-0/+1
| | | | llvm-svn: 160322
* Don't crash when emitting fixits following Unicode characters.Jordan Rose2012-07-161-1/+17
| | | | | | | | | | | | | | | 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> llvm-svn: 160319
* Be lax about trailing whitespace when checking fixit formatting, this ↵Benjamin Kramer2012-07-121-2/+2
| | | | | | | | | | 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. llvm-svn: 160113
* PR13312: Don't crash when printing a fixit that ends in a unicode character.Benjamin Kramer2012-07-121-0/+15
llvm-svn: 160112
OpenPOWER on IntegriCloud