Andy2 977feada82 use a reference to a byte array in the java heap (locking down the ... object) rather than allocating a new array in the C heap -- for the DAWG data of a dictionary. This can use up to 5% of the java heap for huge dictionaries, but I'm hoping it fixes a problem reported by a user of the large German dictionary that seems to involve allocation. If I'm reading correctly, as long as I stay within 16M (24M or more on newer devices) I'm sure to get my memory in the java world while it's less a sure thing in the JNI world (where in addition linux's aggressive overallocation is used, meaning I'll fail when I try to swap in memory on write rather than get back NULL from malloc.)		2011-01-31 18:56:20 -08:00
..
scripts	improve script. Allow pass either branch or tag on commandline,	2010-11-07 08:16:36 -08:00
XWords4	use a reference to a byte array in the java heap (locking down the	2011-01-31 18:56:20 -08:00
Application.mk	initial checkin of jni source and build scripts for android port	2010-01-02 19:10:08 +00:00
INSTALL.txt	fix for new location. Need to get this out of git somehow.	2010-06-07 06:11:11 -07:00