Name: rmT116609 Date: 11/10/2003


A DESCRIPTION OF THE REQUEST :
Given the recent but very limited introduction of the CharSequence
interface, it seems that many parameters of type String are
candidates for being generalized to being of type CharSequence.

The highest priority candidates are those parameters whose values
are likely to come from larger strings (in String objects that
otherwise have to be "substringed," or in character (or byte)
arrays that otherwise have to converted into String Objects),
and whose methods are likely to be called frequently.

(java.lang.<numeric type>.parse...(...) methods and java.io I/O
methods are covered in separate enchancement requests.)



JUSTIFICATION :
A. It seems a logical part of the introduction of CharSequence.

B. Callers working with CharSequence wouldn't have to create
    String objects before making calls.
(Incident Review ID: 224696)
======================================================================