Re: [Java-gnome-developer] Use of destroy()

[Robert M. <ro...@ma...>]

On Sat, 2004-10-30 at 13:06, Jerry Haltom wrote:
> It does. The "problem" as I see it though is Java does not allow you to
> store pointers natively: period. It's stored as an 'int' now, which is
> guarenteed signed 32 bit on ALL PLATFORMS. There is discussion on
> changing it to a long, which is signed 64 bit ON ALL PLATFORMS. There is
> no "native pointer". It would be nice though! THere is talk on putting
> it in a long I think, or a class. I think they both suck though. With a
> long you can't fit it all in a register, with a class you have to
> derefrence (vtable lookup).
> 

Another solution can be define both fields (int and long) and let the
native code decide which one to use. But will the performance increase
enough to allow the extra memory usage?
 
________________________________________
Robert Marcano