Hi all,
JVMTI is a great step forward to supporting extensible profiling and
debug tools. I believe that we should work to ensure that Apache Harmony
implements all JVMTI functionality including optional functionality in
the JVMTI specification. This will ensure that all tools implemented to
the J
On Tue, 2005-09-13 at 17:27 +0100, Tim Ellison wrote:
> [Snip]
> > I guess a requirement for such a component manager would be that it can
> > load and connect components at runtime and that the specific
> > implementations which are loaded can be configured. It might also be
> > good if the same
David Tanzer wrote:
> Since we already started to define some component interfaces I think we
> also should start thinking about a component model which loads /
> connects such components. Maybe there are also some existing solutions
> we might want to look at (I must confess I didn't really searc
Archie Cobbs wrote:
> Santiago Gala wrote:
>
>> IIRC, the (JVM spec v2) requirement for .equals String literals to be
>> (==)identical only holds for Strings in the same .class file, but I
>> could be wrong.
>
>
> I believe the requirement is stronger than that. Any two
> String literals (i.e.,
Hello,
> It is useful to be able to specify certain characteristics of the
> virtual memory regions, eg that the nursery is at higher addresses,
> because the efficiency of the read and write barriers depends on being
> able to quickly identify nursery objects, and having the nursery in high
> add
> I don't see why both methods of memory allocation and clean up may not
be
> employed. The classLoader may manage it's own memory area and create
> objects that only it uses in the main memory area. The main memory area
> objects would be true objects and be gc'ed just like normal (So long as
> th
