<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
Hi Galder, <br>
<br>
Since my last message about JDK 9 build b88, a number of new JEPs
have been integrated into JDK 9 b93 <br>
available <a href="https://jdk9.java.net/download/">here</a>. I'd
like to point you to a few that are now available for testing in
this JDK 9 Early Access build: <br>
<br>
JEP 254: Compact Strings (<a class="moz-txt-link-freetext"
href="http://openjdk.java.net/jeps/254">http://openjdk.java.net/jeps/254</a>)
<br>
<br>
This JEP adopts a more space-efficient internal representation for
strings. <br>
<br>
We propose to change the internal representation of the String class
from a UTF-16 char array to a byte array plus an encoding-flag
field. The new String class will store characters encoded either as
ISO-8859-1/Latin-1 (one byte per character), or as UTF-16 (two bytes
per character), based upon the contents of the string. The encoding
flag will indicate which encoding is used. <br>
<br>
JEP 165: Compiler Control (<a class="moz-txt-link-freetext"
href="http://openjdk.java.net/jeps/165">http://openjdk.java.net/jeps/165</a>)
<br>
<br>
This JEP proposes an improved way to control the JVM compilers. It
enables runtime manageable, method dependent compiler flags.
(Immutable for the duration of a compilation.) <br>
<br>
Method-context dependent control of the compilation process is a
powerful tool for writing small contained JVM compiler tests that
can be run without restarting the entire JVM. It is also very useful
for creating workarounds for bugs in the JVM compilers. <br>
<br>
JEP 243: Java-Level JVM Compiler Interface (<a
class="moz-txt-link-freetext"
href="http://openjdk.java.net/jeps/243"><a class="moz-txt-link-freetext" href="http://openjdk.java.net/jeps/243">http://openjdk.java.net/jeps/243</a></a>)
<br>
<br>
This JEP instruments the data flows within the JVM which are used by
the JIT compiler to allow Java code to observe, query, and affect
the JVM's compilation process and its associated metadata. <br>
<br>
JEP 268: XML Catalog API (<a class="moz-txt-link-freetext"
href="http://openjdk.java.net/jeps/268">http://openjdk.java.net/jeps/268</a>)
<br>
<br>
This JEP develops a standard XML Catalog API that supports the OASIS
XML Catalogs standard, v1.1. The API will define catalog and
catalog-resolver abstractions which can be used with the JAXP
processors that accept resolvers. <br>
<br>
Existing libraries or applications that use the internal API will
need to migrate to the new API in order to take advantage of the new
features. <br>
<br>
<br>
Rgds, Rory<br>
<pre class="moz-signature" cols="72">--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland </pre>
</body>
</html>