harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Liang <richard.lian...@gmail.com>
Subject Re: [classlib] compatibility nuances
Date Fri, 14 Jul 2006 13:56:30 GMT


Geir Magnusson Jr wrote:
> Alexey Varlamov wrote:
>   
>> 2006/7/14, Richard Liang <richard.liangyx@gmail.com>:
>>     
>>> Magnusson, Geir wrote:
>>>       
>>>>> -----Original Message-----
>>>>> From: Alexei Zakharov [mailto:alexei.zakharov@gmail.com]
>>>>> Sent: Thursday, July 13, 2006 10:19 AM
>>>>> To: harmony-dev@incubator.apache.org; geir@pobox.com
>>>>> Subject: Re: [classlib] compatibility nuances
>>>>>
>>>>>
>>>>>           
>>>>>>  That our "not in any particular
>>>>>> order" is different than the "not in any particular order"
>>>>>>
>>>>>>             
>>>>> that the RI
>>>>>
>>>>>           
>>>>>> does?  I'm not trying to make light of it, but it sounds like all
is
>>>>>> correct.
>>>>>>
>>>>>>             
>>>>> Right, from the spec point of view everything is correct.  But I'd
>>>>> like to say that our particular order differs from RI particular order
>>>>> (and such behavior conforms to spec). My next statement is: there are
>>>>> stupid apps that rely on the particular order
>>>>> returned by RI (regardless of spec). I know one already. The question
>>>>> is: should we care or not?
>>>>>
>>>>>
>>>>>           
>>>> Can you figure out what their order is?  If so, I'd use that since we
>>>> are free to do what we want, and if someone does depende on this, it's
>>>> one less change, and it's spec compliant.
>>>>
>>>>
>>>>         
>>> As well as I know,  the order is what the methods are declared in java
>>> source. (Cannot find any document currently ;-) )
>>>       
>> IIRC, Sun and JRockit behave differently to this matter, JRockit's VM
>> reports methods in reversed order. Besides, there are 2 APIs:
>> getDeclaredMethods() and getMethods() - we should consider both if we
>> really care. And detecting "right" order for the last is tedious -
>> taking into account variety of heritable methods (declared directly,
>> inherited from superclass(es), inherited from superinterface(s),
>> inherited from superinterfaces of superclasses).
>>     
>
> What does j9 do?
>
>   
For getDeclaredMethods(), J9 has the same behavior as RI. For 
getMethods, J9 and RI behave differently.   ;-)   But it's not so hard 
to summarize RI's rule of method order. Am I wrong?

Best regards,
Richard
>> I believe we need a bit stronger motivation for scratching this issue,
>> than a blunt testcase - some real-world application.
>>     
>
>
> I agree that this isn't a critical issue, but a "nice to have".  Maybe
> we see what J9 does, and follow the majority (if we spend the time...)?
>
> geir
>
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
>
>
>   

-- 
Richard Liang
China Software Development Lab, IBM 


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message