Check in tests whether error really was written, by setting it to
undefined before each call.

This is a data type to deal with frequently appending to a string.

When a tag is made known to the Validator, which it already knows, the
old id is returned and nothing is added.
As this has to be checked by iterating over all known tags, a new helper
function is written for both SH_Validator_check_tag and
SH_Validator_register_tag: SH_Validator_get_tag.

Because we want also to test this function, we have to include
validator.c in the test file and override the static keyword by an empty
macro. It isn't possible any more to check for correct overflowdetection
by setting the index to UINT_MAX, because it will be iterated over all
data, thus raising an SIGSEGV when doing so. This is solved by filling
garbage unil UINT_MAX is really reached. As there would be an timeout
and it would fill RAM with around 40 GB of garbage, UINT_MAX is
overriden prior to inclusion of validator.c .

Validator serves as an syntax checker, i. e. it can be requested whether
a tag is allowed.

Tests are done using check, allowing to integrate the tests into the
Autotools.
Methods that are part of another unit, but are called in this unit
aren't tested as this would interfere with the idea of unittests. This
also applies for purely wrapper functions, where a call is passed to
another unit.