incubator-kato-spec mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stuart Monteith <>
Subject Re: Replacing ImagePointer references in the Java Runtime API - first pass
Date Mon, 11 Jan 2010 11:15:24 GMT
     Sorry, I should have been more explicit. If all a Handle is is the 
type and the
address, what does this add on top of the types there already - 
JavaObject, JavaClass, etc.

Of course you couldn't get a JavaObject from every entity in the API, 
that sounds confused...
I'd posit that what the Handle adds is an explicit means of storing the 
references to objects
without doing the work to create a working JavaObject, or whatever type 
it is.


Steve Poole wrote:
>> >  Hi,
>> >      I've just been wondering, what's the difference between a Handle and,
>> >  for example, the
>> >  JavaObject that generated it?
>> >
>> >  Interesting..  can you get an JavaObject for every entity in the API?
> For those impls where we've proposed they can provide handles that also
> implement ImagePointer -  wouldn't you end up with a clunky implementation?
> There would be about 30 methods all told inherited from both interfaces!

Stuart Monteith

View raw message