Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #33807

Re: To deprecate or not

Show all headers | View raw

On Saturday, February 13, 2016 at 11:02:40 AM UTC-5, Arne Vajhøj wrote:
> The implementation code would need to be in the class implementing the
> interface not the interface itself (unless Java 8 and marked as
> default).
> 
> Arne

Correct.  I haven't come across a reason to deprecate an interface method like that, but that will work in Java 8+, which everyone ought to be using by now since Java 7 and older is unsupported and unsecure.  Surely there's some government agency running old Java because red tape won't let them update, but if their machines have internet access they're not secure, or there's some other firewall limiting what they can do.  I wouldn't expect government to be secure after the recent hacks against them.

Naturally deprecating the method in the interface with a runtime error is a hack to find calls to the now invalid method.  Is it the best way?  Unlikely, but what else can you do?  Are there other interfaces which extend the parent?  How many classes may be calling this now invalid method?

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

To deprecate or  not mike <mikaelpetterson@hotmail.com> - 2016-02-12 01:16 -0800
  Re: To deprecate or  not Eric Douglas <e.d.programmer@gmail.com> - 2016-02-12 05:59 -0800
    Re: To deprecate or not Arne Vajhøj <arne@vajhoej.dk> - 2016-02-13 11:02 -0500
      Re: To deprecate or not Eric Douglas <e.d.programmer@gmail.com> - 2016-02-15 05:12 -0800
        Re: To deprecate or not Arne Vajhøj <arne@vajhoej.dk> - 2016-02-15 11:42 -0500
  Re: To deprecate or not Arne Vajhøj <arne@vajhoej.dk> - 2016-02-13 11:34 -0500
  Re: To deprecate or  not Andreas Leitgeb <avl@logic.at> - 2016-02-15 00:53 +0000

csiph-web