public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Robert Lougher" <robert_lougher@hotmail.com>
To: dholmes@dltech.com.au, archie@dellroad.org
Cc: brawer@dandelis.ch, chris@kiffer.eunet.be, aph@redhat.com,
	classpath@gnu.org, mauve-discuss@sources.redhat.com
Subject: RE: ClassLoader.findLoadedClass (was: ServiceFactory)
Date: Wed, 24 Mar 2004 10:40:00 -0000	[thread overview]
Message-ID: <BAY10-F35Zpdp9O3oUO0000e60c@hotmail.com> (raw)

Yes, I agree (but see my comment below).  Iin fact, I suggested moving 
findLoadedClass to the VMClassLoader in my last post.  The next release of 
JamVM, which should be out tonight, will have this.  This means releasing a 
modified ClassLoader as a "VM class" but it'll be a while before this makes 
it into the next release of Classpath.

Thanks,

Rob.

----Original Message Follows----
From: "David Holmes" <dholmes@dltech.com.au>

...

>VMClassLoader can define a default mechanism using hashtables or just leave
>things native.
>

A pure Java "reference" implementation won't work.  At the Java level 
VMClassLoader can only keep track of classes defined by a loader (when it 
calls VMClassLoader.defineClass). A call back will be needed so that the VM 
can record a loader as an initiating loader for a class.

>Or in simple words: move the lookup table out of ClassLoader into
>VMClassLoader.


David Holmes

_________________________________________________________________
Use MSN Messenger to send music and pics to your friends 
http://www.msn.co.uk/messenger

             reply	other threads:[~2004-03-24 10:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-24 10:40 Robert Lougher [this message]
2004-03-25  0:02 ` David Holmes
  -- strict thread matches above, loose matches on Subject: below --
2004-03-22 13:15 Robert Lougher
2004-03-23  0:44 ` David Holmes
2004-03-23 17:25   ` Archie Cobbs
2004-03-23 23:59     ` David Holmes
     [not found] <NFBBKALFDCPFIDBNKAPCIEFEDPAA.dholmes@dltech.com.au>
2004-03-22  8:14 ` Sascha Brawer
2004-03-22  9:16   ` Sascha Brawer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BAY10-F35Zpdp9O3oUO0000e60c@hotmail.com \
    --to=robert_lougher@hotmail.com \
    --cc=aph@redhat.com \
    --cc=archie@dellroad.org \
    --cc=brawer@dandelis.ch \
    --cc=chris@kiffer.eunet.be \
    --cc=classpath@gnu.org \
    --cc=dholmes@dltech.com.au \
    --cc=mauve-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).