[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Classpath build process and VM-specific issues
From: |
Ingo Prötel |
Subject: |
Re: Classpath build process and VM-specific issues |
Date: |
Tue, 30 Mar 2004 09:17:42 +0200 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 |
Hi!
We have our own version of the classes in java.lang.* so this dicussion is not
vital for us.
For us it is important that after the initial memory allocation there is no further memory
allocation. So if we need to store native information we need to put it into the Java heap. To do
this we allocate the required memory in the Java heap and mark it as a Java object of type Object.
This allows us to handle this object like every other Java object. So we can store native
information and connect it to a Java object and the garbage collector just frees the memory when the
corresponding Java object is gone.
So we would rather use Object references in such places than byte[]. Byte arrays give programmers on
the Java side the feeling the can work with the content where they really should not touch it.
Cheers,
ingo
--
Ingo Prötel address@hidden
aicas GmbH http://www.aicas.com
Haid-und-Neu-Str. 18 phone +49 721 663 968-32
76131 Karlsruhe fax +49 721 663 968-93
Germany
- Re: Classpath build process and VM-specific issues, (continued)
Re: Classpath build process and VM-specific issues, Robert Lougher, 2004/03/29
Re: Classpath build process and VM-specific issues, Robert Lougher, 2004/03/29