3 commits

Author	SHA1	Message	Date
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
Eric House	eb9ef738e4	remove comms/transport from using thread->env map	2020-04-26 13:39:21 -07:00
Eric House	49242f78cf	more script fixes; move jni code	2017-01-18 07:27:23 -08:00

Renamed from xwords4/android/XWords4/jni/xportwrapper.h (Browse further)