|
Yes. As I said before, this code has
changed. If you are writing your own JNI natives or code that expects this
structure to look this way, you are dead. It is different. You need
to check the code from HEAD or find another way to do what you are doing that
doesn't use internal API.
1) I was aware of that, the "internal" in the package
name gives it away.
2) I'm working
with 2.1 code. Do you foresee any compatibility issues if I use this new
method with a 2.1 codebase?
-----
1) You are using internal
API so it is subject to change without notice
2) It has changed! Check out the latest code from HEAD.
<Matthew_Hatem@xxxxxxxxxxxxxxxxx>
wrote in message news:bek3fh$ec0$1@xxxxxxxxxxx....
Please forgive me if
this is a dumb question:
Is this the standard way to process structs that posess TCHARs?
I'm working with a struct that has a few of these and one is of size
256. Is there a better way?
//
TCHAR lfFaceName[LF_FACESIZE];
public
char
lfFaceName0, lfFaceName1, lfFaceName2,
lfFaceName3,
lfFaceName4,
lfFaceName5, lfFaceName6, lfFaceName7,
lfFaceName8, lfFaceName9, lfFaceName10,
lfFaceName11,
lfFaceName12, lfFaceName13, lfFaceName14, lfFaceName15,
lfFaceName16, lfFaceName17, lfFaceName18,
lfFaceName19,
lfFaceName20, lfFaceName21, lfFaceName22, lfFaceName23,
lfFaceName24, lfFaceName25, lfFaceName26,
lfFaceName27,
lfFaceName28, lfFaceName29, lfFaceName30, lfFaceName31;
|