Hi Jeroen,
On Thu, 2005-07-28 at 10:52 +0200, Jeroen Frijters wrote:
I agree that the call to registerInitiatingLoader() in
ClassLoader.defineClass() is a bit iffy. The reason I left it in there
is to not break any VMs when I check in this patch. I was a bit
surprised by the fact that two
Archie Cobbs wrote:
For what it's worth, JCVM maintains its own intiated types and
defined types tables internally, so this patch does not make life
better (or worse). I would have to disable this code.
This raises the question, how many VMs are actually using the
loadedClasses hashtable in
Mark Wielaard wrote:
But for a larger change like this it is probably good to get a sign-off
by Robert, Stephen, Archie or any other runtime implementor who you know
uses pristine Class/ClassLoader classes from GNU Classpath to make sure
they agree that they will keep on using them. Or hear from
David Gilbert wrote:
I hope when I mentioned that JamVM was broken, it didn't sound like a
complaint, because that wasn't what I intended.
Not at all. I was just a bit surprised that it is possible to live on
the bleeding edge of development and still maintain the notion:
how VMs work...as
