(Note: should be removed later / merged into ipaaca-tester-cpp).

Initial basic version for a 'multitool' console test battery.
For now, it implements a simple sniffer (with output similar
to ipaaca-iu-sniffer).
Planned: switching mode (sniffer, injector, modifier ...)
per command-line or interactively with keys; also implement
other language versions.

Caveat for sniffer function: resend_requests trigger ADDED event
twice (once for the sniffer "" scope, once for the hidden one).

(since RSB-Python only supports the unsigned version)

Also renamed '__...' fields for default loggers to '_...'

It is now identical to the other language versions (again).
The new name is not as nice semantically speaking, but changing
the Python version is the path of least resistance.

Recent addition of IntegerConverter in rsb0.14 seems flaky (it
seems Python will always send 64bit, and no conversion can be made),
-> now using 64bit types for transport everywhere revision numbers
are exchanged as an RPC result, i.e. all RemoteIU modifications
and ResendRequests (Also disabled our own legacy IntConverters).

Note: the ipaaca.proto Protobuf definition has not been changed,
for compatibility reasons. Java version contains explicit (int)
casts when protobuf objects are built. (TODO Discuss proto->64bit)

Tests between all three languages work (Netboot, rsb0.14,
protobuf2.6.1, spread4.4), tested with WOz+Cere+Billie.

Also set back to java8 (Android is supposed to support it now
and it turns out our tests failed since they use a lambda...).

Read access in locked payloads is performed on queued operations
before searching the old database. Threads other than the locking
thread consistently read the old information.

On POSIX, default Lock now also uses boost::thread (instead of pthread)
pthread linkage is still present for legacy wrapping.

ATTENTION: unlocked payload writing is (by design) not thread-safe
(won't crash but data might be inconsistent). Please use Locker armors
around all code that might modify a payload in more than one thread.
---> #1: Always use Locker in IU handlers that write to existing IUs!!

For string values, ONLY the empty string "" maps to false
(previously, "false", "False", and "0" also mapped to false)
For list and map values, zero-element ones now map to false
(previously, any list or map would map to true).

The new semantics are identical to Python behavior for your convenience,
since they were not generically prescribed by the STL anyway.

It will call the teardown stuff then os._exit(...). Later, when the
backends are fixed, we could simply alias it to sys.exit again.

Usage:
 - use ipaaca.exit() at the end of every python script
 - do not forget to catch errors as well as KeyboardInterrupt and
   SystemExit (or their default handlers will hang at exit time, too)
 - you can call ipaaca.exit with ant int argument (like sys.exit etc.)

Also re-renamed the other two back to --rsb-host and --rsb-port ;)

Change was requested to accommodate people who package the
directory from outside the soa script (i.e. standard tools ;) )

!!! Please update the rsb package accordingly. !!!

End users need not change very much. (Please update rsc/rsb
version numbers in CMakeLists.txt in your own C++ projects).

- Some (internal) changes for rsb0.14 compatibility

(Initial preparation for Android compatibility - incomplete due to rsb)

Arguments:
  --delimiter delim             field delimiter, default '\t'
  --strip                       call strip() in each field first
  --fields name1 [name2 [...]]  fields to print (in order)
                                defaults to: 'time' 'text'

- FutureIU can now use an existing InputBuffer

[.. code ...]
IPAACA_SIMPLE_TIMER_BEGIN(blockid1)
[... first code block to time ...]
IPAACA_SIMPLE_TIMER_END(blockid1, "Processing loop 1")
[...]

-> e.g.: "Processing loop - us elapsed: 15" to terminal

Several blocks can be timed in one stack frame using more blockids
(TODO: implement profiling mode that can be turned on/off)