[#JRUBY-558] Integration method matching needs more help with nulls

JRuby

Integration method matching needs more help with nulls

Created: 04/Feb/07 02:51 PM Updated: 15/Feb/08 12:55 PM

Component/s:

Java Integration

Affects Version/s:

JRuby 0.9.8

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

java

Description

« Hide

Given a class / interface of the form:

Foo aMethod(SomeClass1 a);
Foo aMethod(SomeClass2 b);

the following jruby code:

x.aMethod(nil)

has insufficient information to choose between the two methods (the first found is used).

The java solution is:

x.aMethod((SomeClass1) null);

Which may inform a jruby solution.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Charles Oliver Nutter - 18/Apr/07 04:52 AM

An upcoming library from Rhino that uses Java specified overloaded method selection behavior may help this, as might our future rework of Java integration, but neither of those will happen until after 1.0.

[ Permlink | « Hide ]

Charles Oliver Nutter - 30/Sep/07 10:26 AM

We should revisit and try to find a solution for this in the 1.1 timeframe.

[ Permlink | « Hide ]

Charles Oliver Nutter - 15/Feb/08 12:55 PM

Removing target release from issues that fit any of the following criteria:

No known way to fix them
Java integration enhancements out of scope for 1.1 release
Other out of scope issues for 1.1