Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Eric Sosman Newsgroups: comp.lang.java.programmer Subject: Re: Calling deprecated methods Date: Tue, 12 Dec 2017 15:41:40 -0500 Organization: A noiseless patient Spider Lines: 37 Message-ID: References: <9db47be9-1c38-48a9-bad9-9799f54df59a@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Tue, 12 Dec 2017 20:41:43 -0000 (UTC) Injection-Info: reader02.eternal-september.org; posting-host="8772053e4e65df557d654b4ba66908c5"; logging-data="12708"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19ClKRxIoUTjxDgzBgXXdoE" User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 In-Reply-To: Content-Language: en-US Cancel-Lock: sha1:BNctjFkK3v9gZ2sMtxeyzzGiXIk= Xref: csiph.com comp.lang.java.programmer:37818 On 12/12/2017 3:05 PM, Kiwi User wrote: > On Tue, 12 Dec 2017 10:24:50 -0800, Eric Douglas wrote: >> [...] >> The fact they deprecated a method isn't a problem. The fact they're >> still calling it is questionable. javax.swing.JTree calls >> java.awt.event.MouseEvent.getModifiers() which is marked deprecated in >> Java 9. >> > Agreed. At a minimum, everything in the package should use the > replacement class/method and preferably all code in the next release > should use it too. > > This is the "eat your own dogfood" principle and I'm suspicious of those > who don't stick to it. Bear in mind that Java 9 was originally scheduled for 2016, then postponed to 2017 Spring, then 2017 Summer, and finally to 2017 Autumn, more than a year later than planned.[*] Resistance to the Project Jigsaw changes can be blamed for only part of the delay; we may imagine that there was a lot of work to be done and that it took substantially longer than expected. Deadline pressure being what it is, I don't find it surprising that the final product was not quite as polished as might have been hoped; it's quite possible that a goodly number of lower-priority tasks were deferred to Another Time. Java's GUI technologies might well be considered among the lower-priority pieces ... [*] A colleague once explained his method for making sense of software project time estimates. An estimate always consists of two parts: A quantity and a time unit, like "two weeks" or "six months." My colleague would start by doubling the quantity, then continue by bumping the time unit up by one step. Thus, the examples above would be understood as "four months" and "twelve years." ;) -- esosman@comcast-dot-net.invalid Eleven hundred thirty-five days to go.