On Tue, 3 Nov 2020 22:25:08 GMT, Magnus Ihse Bursie wrote:
> With clang 10.0, the compiler now detects a new class of warnings. The
> `misleading-indentation` warning has previously been disabled on gcc for
> hotspot and libfdlibm. Now we need to disable it for clang as well.
Why do we disabl
m to
run their businesses on. A lot of businesses are still running on JDK-8
for this reason.
Running bleeding edge software might be an option for a single desktop
user, but not in an enterprise environment with thousands of users
or in a critical environment like the booking system of an ai
I haven't found a case where the cache adds notable overhead, but I'll
try to get back soon with more data
Best regards,
Adrian
On Tue, Sep 15, 2015 at 11:31 AM, Peter Levart wrote:
> Hi Adrian,
>
> I looked briefly at your code and claims and have some comments inline...
>
d said "There was a lot of experiments
and prototypes in the past along these lines" - are the results
public?
He also mentioned improving classloading in Java's upcoming module
system (originally planned for Java 7, currently delayed to Java 9),
but I believe the algorithmic complexity and performance of
URLClassLoader could be improved without complicated changes
Please let me know what you think, and thanks for your time!
Best regards,
Adrian
and I tried to explain the
"why" in my comments in the code
Any insight on why this would/wouldn't work or wouldn't be ideal would
be greatly appreciated
I'm just trying to get a better understand of how JVM (classloading)
works, why it works that way, and how it could b
ecessary
Of course, I could be wrong, or more needs to be considered, but I
thought it was worth bringing up and get some feedback.
Maybe someone could confirm the behaviour of sendfile/splice, or
explain the reasoning for checking the size in the JVM?
Thank you for your time!
Best regards,
Adrian
