Re: [cp-patches] [RFA/JDWP] IdManager

2005-06-21 Thread Keith Seitz
On Mon, 2005-06-20 at 13:48 -0500, Archie Cobbs wrote: Uniquely identifies a reference type in the target VM. It should not be assumed that for a particular class, the classObjectID and the referenceTypeID are the same. A particular reference type will be identified by exactly one ID in

Re: [cp-patches] [RFA/JDWP] IdManager

2005-06-21 Thread Keith Seitz
On Tue, 2005-06-21 at 14:08 -0500, Archie Cobbs wrote: You're definition of type then is the static (compile time type). But in Java Class objects are associated with runtime types, not compile time types. I've been confused about this before and went so far as to document it so I wouldn't

Re: [cp-patches] [RFA/JDWP] IdManager

2005-06-20 Thread Keith Seitz
On Mon, 2005-06-20 at 10:22 -0500, Archie Cobbs wrote: Keith Seitz wrote: + /* Mapping of class (Class) to IDs (ReferenceTypeId) for reference + types. Unlike other types, reference id types are NEVER released. */ + private Hashtable _classTable; Another question born from my own

Re: [cp-patches] [RFA/JDWP] IdManager

2005-06-20 Thread Archie Cobbs
Keith Seitz wrote: + /* Mapping of class (Class) to IDs (ReferenceTypeId) for reference + types. Unlike other types, reference id types are NEVER released. */ + private Hashtable _classTable; What if a class(loader)s are garbage collected? Would this hash table then become a memory