Hi,
during bootstrap we load and use at least two of the jrt, file and jar
URLStreamHandlers via URL$DefaultFactory. Avoiding use of reflection to
instantiate these slightly speed up bootstrap by reducing number of
classes loaded and doing fewer relatively expensive reflective
operations:
http:/
On 02/01/2019 09:02, Claes Redestad wrote:
Hi,
during bootstrap we load and use at least two of the jrt, file and jar
URLStreamHandlers via URL$DefaultFactory. Avoiding use of reflection to
instantiate these slightly speed up bootstrap by reducing number of
classes loaded and doing fewer relativ
Hi,
On 2019-01-02 11:04, Alan Bateman wrote:
On 02/01/2019 09:02, Claes Redestad wrote:
Hi,
during bootstrap we load and use at least two of the jrt, file and jar
URLStreamHandlers via URL$DefaultFactory. Avoiding use of reflection to
instantiate these slightly speed up bootstrap by reducing n
On 02/01/2019 10:43, Claes Redestad wrote:
:
While we're in the area then it would be nice to eliminate the use of
Class::newInstance too - if each of the built-in protocol handlers is
public with a public no-arg constructor then
getConstructor().newInstance() should do it.
To be perfectl
