To disambiguate calls to overloaded methods and constructors, ABL handles scenarios that go beyond basic differences in the number, mode, and data types of parameters in order to determine a match. For example, some parameter data types, such as temp-table and object types, can involve complex matching scenarios that are not resolved until run time, or can require resolving the best of several matching scenarios at compile time.