This is the mail archive of the
java-discuss@sourceware.cygnus.com
mailing list for the Java project.
Re: CNI namespace
- To: Per Bothner <per at bothner dot com>
- Subject: Re: CNI namespace
- From: Tom Tromey <tromey at cygnus dot com>
- Date: Mon, 3 Apr 2000 12:14:53 -0700 (PDT)
- Cc: java-discuss at sourceware dot cygnus dot com
- References: <y683dpaetn2.fsf_-_@ignucius.devel.redhat.com><m2r9ct8pho.fsf@kelso.bothner.com>
>> I'm continuing the work on the C++ CNI->JNI translation layer, and
>> such a change would create a cleaner solution to the problem of
>> conflicting CNI and JNI types.
Per> What is "the problem of conflicting CNI and JNI types"?
In some situations it is useful for a CNI "jobject" and a JNI
"jobject" to be different. For instance, this is the case if we have
a precise, copying collector that doesn't have the ability to lock
down an object.
For primitive types I'm not so concerned. The definitions we use
there preserve source and binary compatibility.
Tom