public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "David Holmes" <dholmes@dltech.com.au>
To: "Robert Lougher" <robert_lougher@hotmail.com>
Cc: <classpath@gnu.org>, <mauve-discuss@sources.redhat.com>
Subject: RE: ClassLoader.findLoadedClass (was: ServiceFactory)
Date: Thu, 25 Mar 2004 00:02:00 -0000	[thread overview]
Message-ID: <NFBBKALFDCPFIDBNKAPCEEIEDPAA.dholmes@dltech.com.au> (raw)
In-Reply-To: <BAY10-F35Zpdp9O3oUO0000e60c@hotmail.com>

Robert Lougher wrote:
> Yes, I agree (but see my comment below). >
> ...
> 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.

Well you don't need an explicit callback as that's likely to be VM specific.
The VM can directly access the Java-level hashtable(s) if it needs to using
JNI or whatever means that particular VM has. The only thing you need in the
reference implementation is a comment saying that the VM must keep the
tables up to date.

That said, I don't see much value in a "reference implementation" for this
particular feature.

David Holmes

  reply	other threads:[~2004-03-25  0:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-24 10:40 Robert Lougher
2004-03-25  0:02 ` David Holmes [this message]
  -- 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=NFBBKALFDCPFIDBNKAPCEEIEDPAA.dholmes@dltech.com.au \
    --to=dholmes@dltech.com.au \
    --cc=classpath@gnu.org \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=robert_lougher@hotmail.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).