RawData ?

Tue Apr 8 21:06:00 GMT 2003

Tom Tromey <tromey@redhat.com> writes:
> >>>>> "Michael" == Michael Koch <konqueror@gmx.de> writes:
>> Michael> Execept the copyright statement and package name both java
> Michael> files are identical. Thats why I thought they could be
> Michael> merged.
>> I've been wondering, but haven't yet brought up, whether this is
> something Classpath really wants to do. It imposes a cost on all
> implementing VMs, and compilers.
>> Note that we don't even handle RawData properly -- for instance I
> think `Object foo = <Rawdata>' should be invalid. Any cast to RawData
> should also be rejected by the compiler.
>> Likewise the interpreter and verifier probably need special cases
> here. There may be other problems, in reflection or JNI. I'm not
> sure.

I don't follow. This is just a placeholder for some sort of native
data accessible to the JVM but not to anyone else. Using a class is
natural since you can use an api like the native state api in
classpath to attach native data to the java class. I don't see
anything really special here except perhaps insuring garbage
collection works appropriately.
Brian
-- 
Brian Jones <cbj@gnu.org>