[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cp-patches] FYI: ClassLoader caching Part 2
From: |
Jeroen Frijters |
Subject: |
RE: [cp-patches] FYI: ClassLoader caching Part 2 |
Date: |
Mon, 25 Jul 2005 18:17:19 +0200 |
Jeroen Frijters wrote:
> Mark Wielaard wrote:
> > 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.
>
> Like Archie says, your comment doesn't make sense ;-) If a VM decides
> not to use the cache in ClassLoader, it replaces VMClassLoader and
sets
> the constant to true.
Oh, I'm sorry, I think see what you mean. If a VM would take a binary
GNU Classpath jar, it wouldn't be able to override the value of the
flag.
Is this an important scenario? I thought you long haired types didn't
like binary distributions ;-)
Regards,
Jeroen