Eric House 9cdd5a7b72 share mpool and vtable in jni calls ... A number of jni calls were "stateless", which meant they allocated their own vtmgr and mpool instances each time invoked. Instead invoke them with the global jni closure and add to it vtmgr (already has mpool) and use these instead of allocating/freeing each time. To make sure no race conditions are introduced (mpool, though debug-only, is probably not thread-safe), guard these new uses with an in-use flag. If that fires I'll need a mutex or something.		2018-06-27 21:17:44 -07:00
..
android	share mpool and vtable in jni calls	2018-06-27 21:17:44 -07:00
common	init variable	2018-06-13 14:34:31 +03:00
dawg	put back a couple of words -- not dirty!	2017-05-05 06:48:52 -07:00
debian	ignore debian build files	2012-01-04 18:11:29 -08:00
linux	test script tweaks	2018-06-18 07:11:38 -07:00
newrelay	beginnings of new relay: shows persistence	2017-11-05 19:24:41 -08:00
relay	track and log types of (un-acked) messages	2018-05-24 21:03:25 -07:00
scripts	more work on script	2014-02-26 07:52:18 -08:00
tests	allow to run multiple games at once	2005-09-14 05:12:07 +00:00
wince	make trade and move confirm non-blocking	2017-02-17 08:58:20 -08:00
Makefile	include all .xml and .java files, but only if they're not named in a .gitignore file in the same directory	2014-03-01 11:44:20 -08:00