[LANG-608] Some StringUtils methods should take an int character instead of char to use String API features.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5
• Fix Version/s: 3.0
• Component/s: lang.*

Environment

java version "1.6.0_16"
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)

Microsoft Windows [Version 6.0.6002]

Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700)
Java version: 1.6.0_16
Java home: C:\Program Files\Java\jdk1.6.0_16\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"

• Assignee: Gary D. Gregory
• Reporter: Gary D. Gregory
• Created: 16/Mar/10 00:48
• Updated: 10/Mar/11 22:30
• Resolved: 16/Mar/10 00:50

Description

Change the APIs from char to int character input to match underlying JRE API called. There is no need to narrow the input type argument to the JRE, in fact this causes us to loose support for Unicode supplementary characters. The APIs changed are:

• indexOf(String, char) -> indexOf(String, int)
• indexOf(String, char, int) -> indexOf(String, int, int)
• lastIndexOf(String, char) -> lastIndexOf(String, int)
• lastIndexOf(String, char, int) -> lastIndexOf(String, int, int)
• contains(String, char) -> contains(String, int)

The matches methods like String#indexOf(int)