[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cp-patches] FYI: ClassLoader caching Part 2
From: |
Mark Wielaard |
Subject: |
Re: [cp-patches] FYI: ClassLoader caching Part 2 |
Date: |
Mon, 25 Jul 2005 17:23:32 +0200 |
Hi,
On Mon, 2005-07-25 at 16:29 +0200, Jeroen Frijters wrote:
> I committed the attached patch to complete to ability of the VM to
> bypass the class caching in ClassLoader.
>
> 2005-07-25 Jeroen Frijters <address@hidden>
>
> * java/lang/ClassLoader.java
> (loadedClasses): Set based on VMClassLoader.VM_USE_CACHE.
> (defineClass): Modified to respect VMClassLoader.VM_USE_CACHE.
> * vm/reference/java/lang/VMClassLoader.java
> (VM_USE_CACHE): New field.
This won't work if you make the VM_USE_CACHE field static final. Then
the constant will be compiled into ClassLoader making it impossible to
override for the runtime vm-classes later. It has to be a static method
for that to work.
Aaron and Keith might also want to comment on this since they will need
a way to access the loaded classes of a classloader for their jdwp
interface. So they might want a VMClassLoader.getLoadedClasses() method
if we push the responsibility for tracking this to the runtime.
I do agree allowing the runtime to do all this bookkeeping itself is a
good thing to do in general btw.
Cheers,
Mark
signature.asc
Description: This is a digitally signed message part