Am 02/04/17 um 23:31 schrieb Michael Osipov:
> Am 2017-02-04 um 23:26 schrieb Christian Schulte:
>> Am 02/04/17 um 13:19 schrieb Michael Osipov:
>>> I will merge as-is without further modifiers.
>>
>> Please watch out for this:
>>
>> class A {
>>
>> @Deprecated
>> void methodWithTypo()
>> {
>> this.methodWithoutTypo();
>> }
>>
>> void methodWithoutType()
>> {
>> // do what the old method did
>> }
>>
>> }
>>
>> External usage:
>>
>> class B extends A {
>>
>> @Override
>> void methodWithTypo()
>> {
>> // do something else
>> }
>>
>> }
>>
>> We must not stop calling the deprecated methods because
>>
>> // do something else
>>
>> would no longer be called.
>
> That is true, but your IDE should tell you that your method is
> deprecated. When removed in 4.0, you will ultimately get either a
> compile time or runtime issue. I think this is ok for a new major release.
>
> I see no way how this can be else solved cleanly.
Just do it the other way around. See my other mail. Old method is kept
as is - new method just calls the old method. Needs a @SuppressWarnings
deprecation annotion.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
