[3293] in java-interest
Re: Type and Overload resolution
daemon@ATHENA.MIT.EDU (Ken Arnold - Sun Labs)
Mon Nov 6 17:45:47 1995
Date: Mon, 6 Nov 1995 14:45:22 -0500
From: arnold@cocolat.East.Sun.COM (Ken Arnold - Sun Labs)
To: java-interest@webrunner.neato.org
Yuan Jiang asks:
>I thought Java enforces types strictly. Then I'm confused with the
>method (or the smae name and number of parameters) overload resolution
>scheme:
>
>It uses a parameter-type conversion cost table to determine "which
>matching method has the lowest type conversion cost."
This document (the alpha language spec) is out of date. It is still a
good starting point, but things have changed. This is one of them.
The matching is now done by a "most exact match" strategy, not by
counting conversion cost.
Ken
-
This message was sent to the java-interest mailing list
Info: send 'help' to java-interest-request@java.sun.com
