Page History

The Java programming language supports overloading methods , and Java can distinguish between methods with different method signatures. This means thatConsequently, with some qualifications, methods within a class can have the same name if they have different parameter lists. In method overloading, the choice of which method to invoke be invoked at runtime is determined at compile time. Even if the runtime type differs for each invocation, in overloadingConsequently, the overloaded method invocations depend on associated with the static type of the object at compile time. is invoked even when the runtime type differs for each invocation.

For program understandability, do not introduce ambiguity while overloading (see MET50-J. Avoid ambiguous or confusing uses of overloading), and use overloaded methods sparingly [Tutorials 2013 Wiki MarkupOverloaded methods should be used sparingly, as they can make code much less readable \[[Tutorials 2010|AA. Bibliography#Tutorials 10]\]. Do not introduce ambiguity while overloading, for similar reasons \[[Bloch 2008|AA. Bibliography#Bloch 08]\].

Noncompliant Code Example

This noncompliant code example attempts to use the overloaded display() method to perform different actions depending on whether the method is passed an ArrayList<Integer> or a LinkedList<String>. :

public class Overloader {
  private static String display(ArrayList<Integer> aarrayList) {
    return "ArrayList";
  }

  private static String display(LinkedList<String> llinkedList) {
    return "LinkedList";
  }

  private static String display(List<?> llist) {
    return "List is not recognized";
  }

  public static void main(String[] args) {
    // Single ArrayList
    System.out.println(display(new ArrayList<Integer>()));
    // Array of lists
    List<?>[] invokeAll = new List<?>[] {
        new ArrayList<Integer>(), 
        new LinkedList<String>(), 
        new Vector<Integer>()};

    for (List<?> ilist : invokeAll) {
      System.out.println(display(ilist));
    }
  }
}

...

At compile time, the type of the object array is {{List}}. The expected output is {{ArrayList}}, {{LinkedList}} and {{List is not recognized}} ({{java.util.Vector}} does not inherit from {{java.util.List}}). However, in all three instances {{List is not recognized}} is displayed. This happens because in overloading, the method invocations are not affected by the runtime types but only the compile time type ({{List}}). It is dangerous to implement overloading to tally with overriding, more so, because the latter is characterized by inheritance unlike the former \[[Bloch 2008|AA. Bibliography#Bloch 08]\] ArrayList, ArrayList, LinkedList, and List is not recognized (because java.util.Vector is neither an ArrayList nor a LinkedList). The actual output is ArrayList followed by List is not recognized repeated three times. The cause of this unexpected behavior is that overloaded method invocations are affected only by the compile-time type of their arguments: ArrayList for the first invocation and List for the others.

Compliant Solution

This compliant solution uses a single display method and instanceof to distinguish between different types. As expected, the output is ArrayList, ArrayList, LinkedList, List is not recognized. :

class Overloader {
public class Overloader {
  private static String display(List<?> llist) {
    return (
      llist instanceof ArrayList ? "Arraylist" : 
      (llist instanceof LinkedList ? "LinkedList" : 
      "List is not recognized")
    );
  }

  public static void main(String[] args) {
    // Single ArrayList
    System.out.println(display(new ArrayList<Integer>()));

    List<?>[] invokeAll = new List<?>[] {
        new ArrayList<Integer>(), 
        new LinkedList<String>(), 
        new Vector<Integer>()};

    for (List<?> ilist : invokeAll) {
      System.out.println(display(ilist));
    }
  }
}

...

Applicability

Ambiguous uses of overloading can lead to unexpected results.

Automated Detection

TODO

Related Vulnerabilities

Search for vulnerabilities resulting from the violation of this guideline on the CERT website.

Bibliography

...

...

[API 2013]	Interface Collection<E>
[Bloch 2008]	Item 41, "Use Overloading Judiciously"
[Tutorials 2013]	Defining Methods

 

...

Image Added Image Added Image Added[API 2006|AA. Bibliography#API 06]\] [Interface Collection|http://java.sun.com/j2se/1.4.2/docs/api/java/util/Collection.html] \[[Bloch 2008|AA. Bibliography#Bloch 08]\] Item 41: Use overloading judiciously \[[Tutorials 2010|AA. Bibliography#Tutorials 10]\] [Defining Methods|http://download.oracle.com/javase/tutorial/java/javaOO/methods.html]MET04-J. Ensure that constructors do not call overridable methods      16. Methods (MET)      MET06-J. Do not call overridable methods from a privileged block