Put distance variable to better use in areParametersCompatible() to fix
ambiguity in StringBuffer methods.
This commit is contained in:
parent
41a29eba7a
commit
e387788b36
1 changed files with 11 additions and 4 deletions
|
@ -410,6 +410,12 @@ public abstract class ESLoader extends ESObject {
|
|||
// The simplest case is direct object compatibility
|
||||
sourceClass = params[i].getClass();
|
||||
accepted = targetClass.isAssignableFrom(sourceClass);
|
||||
if (targetClass != sourceClass) {
|
||||
if (targetClass == Object.class)
|
||||
distance += 2;
|
||||
else
|
||||
distance += 1;
|
||||
}
|
||||
debugInfo = " accepted (subclassing)";
|
||||
|
||||
if (!accepted) {
|
||||
|
@ -440,6 +446,7 @@ public abstract class ESLoader extends ESObject {
|
|||
convertToChar = new boolean[n];
|
||||
}
|
||||
convertToChar[i] = true;
|
||||
distance += 1;
|
||||
debugInfo = " accepted (String(1) as Character)";
|
||||
} else {
|
||||
debugInfo = " rejected (String not of length 1)";
|
||||
|
|
Loading…
Add table
Reference in a new issue