CNI namespace

Mon Apr 3 12:15:00 GMT 2000

>> 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