Dr. Torsten Rupp wrote:
I'm currently changing the target native layer to replace the macros by
functions. For this suitable datatypes have to be used in the function
prototypes (as requested in the dicussion). Currently it seems there is
a mixture of native datatypes (e. g. int) and JNI datatypes (e. g. jint
or jlong). First I thought it would be keep out JNI from the target
native layer completely, because the layer should be independent from
JNI (but used in JNI-functions). This seems to be impossible, because e.
g. the datatype jlong which is at least on some systems not available as
a scalar native type (e. g. long long).
My question: what will be the accepted designed for datatypes? Do we
- keep a mixture of native types and JNI types (and accept the
additional code for conversion e. g. from int to jint and back)?
- use only JNI types?
- use only native type?
My opinion.. use both native and JNI types. The specific siutation
will dictate what to do. Uses casts as required. Etc.
This probably sounds simplistic. Maybe a specific example would make
the issue clearer..
-Archie
__________________________________________________________________________
Archie Cobbs * CTO, Awarix * http://www.awarix.com
