Tuesday, August 4, 2015

JEP 260: Encapsulate Most Internal APIs

The JEP 260 is a candidate to be included in JDK 9, this JEP deals with the problem that the modularization effort will have with the current internal APIs.

This JEP define three types of internal APIs:

  1. Non critical internal APIs, this are not critical and will be encapsulated in JDK 9
  2. Critical internal APIs witch supported replacement exists, this APIs are critical, but they have a replacement that was made in JDK 8. 
  3. Non encapsulated critical internal APIs, as Unsafe, this APIs does not have a replacement and are critical, this APIs remain public in JDK 9, but as soon as they have a replacement they could be encapsulated. 
If you need more information read the official JEP 260 page.




No comments:

Post a Comment

Revolutionizing Stream Pipelines with Custom Intermediate Operations JEP 473: Stream Gatherers (Second Preview)

Introduction In the ever-evolving scene of Java improvement, the Stream API has been a foundation of utilitarian programming paradigms sin...