Support for Apple Extensions

[Alan Bateman]

On 05/07/2013 17:44, Johannes Schindelin wrote:
> :
> In addition, we are heavy users of handleOpenFile() and handleAbout(),
> printFiles(), handleQuitRequestWith(), userSessionActivated(),
> userSessionDeactivated(), systemAboutToSleep(), systemAwoke(),
> screenAboutToSleep(), screenAwoke(), appHidden, appUnhidden(),
> appMovedToBackground(), appRaisedToForeground, and appReOpened().
>
> Alan, I think you might be surprised what kind of reactions your
> suggestion to remove -- even parts of -- a well-established, wide-used API
> elicited.
>
> After all, Sun worked very hard -- and successfully so -- on an incredible
> backwards-compatibility, so much so that you can still execute code that
> was compiled for Java 1.1 without *any* problems. That is what makes Java
> so much nicer to use than, say, C# or C++, where you have to adjust things
> all the time just to keep them compiling, let alone running.
>
> Maybe you can explain what benefits there are in removing that established
> API, and maybe you could elaborate why those benefits outweigh the costs?
>
> I am curious,
> Johannes
I haven't proposed removing these APIs. I have instead just asked a few 
questions to try to get some clarity as to their status and also to get 
some understanding as to which of these APIs are used. One motive to 
understanding their supportness is modularity as it's important to know 
which APIs might need to be "exported". See also JEP-179 [1] for the 
proposal to try to capture the support status of APIs so that it is 
clear to both JDK maintainers and to developers using the JDK.

-Alan

[1] http://openjdk.java.net/jeps/179