Eric House 9fa23af6e0 retain thread->env mapping in DEBUG builds only ... I'm keeping it AND asserting at every possible location that the env passed all the way in is the same as what the mapping produces. If in months I haven't seen a single crash then I can evaluate which way of passing the env around is better. (It'd be code size vs. performance, as the passing of env is noticably faster. Code size could be fixed by turning 'XWEnv xwe,' into a macro that goes away on some builds.)		2020-04-26 13:39:21 -07:00
..
android	retain thread->env mapping in DEBUG builds only	2020-04-26 13:39:21 -07:00
common	stop using thread->env mapping for util callbacks	2020-04-26 13:39:21 -07:00
dawg	add option to print a delimiter between tiles	2020-04-24 21:14:20 -07:00
debian	ignore debian build files	2012-01-04 18:11:29 -08:00
linux	stop using thread->env mapping for util callbacks	2020-04-26 13:39:21 -07:00
newrelay	beginnings of new relay: shows persistence	2017-11-05 19:24:41 -08:00
relay	use deviceID to invite via relay; make 3- and 4-device games work	2020-02-16 19:12:22 -08: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
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