Summary: | [content assist] Content Assist fails when escape sequence present | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | andrew |
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | Daniel.Stevens, daniel_megert, dimitris, dirk_baeumer, rgavlin, rotvel |
Version: | 3.1 | ||
Target Milestone: | 3.1 M7 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
andrew
2005-04-06 05:03:20 EDT
Seems to be a bug in the scanner. I will investigate. The problem comes from the handling of escape characters in string literal. *** Bug 91221 has been marked as a duplicate of this bug. *** With the fix for bug 91221, it will look like it works, but the escape handling is boggus as soon as it is using unicodes. Without unicode it should work. The current support is using the unicode support even if there is no unicode. This is boggus and needs to be fixed. The boggus part is escape characters inside string literal. For example, the following code doesn't produce the expected result: public class Test { static String C = "\u005Cn"; public static void main(String[] args) { System.out.print(C.length()); System.out.println(C.charAt(0) == '\n'); } } It returns: 1false instead of: 1true Fixed and released in HEAD. Regression tests added in ScannerTest.test027-035. *** Bug 91780 has been marked as a duplicate of this bug. *** *** Bug 93877 has been marked as a duplicate of this bug. *** Verified for 3.1 M7 using build I20050512-2035 + jdt.core HEAD. *** Bug 96448 has been marked as a duplicate of this bug. *** *** Bug 101804 has been marked as a duplicate of this bug. *** |