GitLab

* Reimplementing destroyLocked as death test
* Comments
* Includes to use < > instead of " "
* Don't use c99-isms.

* Documentation
* Exception texts
* Exception safety for a rare situation

The situations are very bad anyway, and that should not happen during
normal operation. So we assert instead.

The previous looked like it should be boolean (there's something good
about lisp's P suffix).

Because of fear of possible future collisions.

* Removed an unneeded friend declaration.
* Typo

- spacing
- new lines for readability
- const
- brace position for catch
- position of ++/--

It should be the same according to the standard, but Clang seems not to
agree with that.

It seems it isn't portable and it's not very useful check.

And update tests so they lock.

It can be used to check the thing is locked.

The test may be broken by design. In such case, it should be removed.
But it is left there for now, maybe it's just broken implementation and
someone (the reviewer?) may have an idea how to fix it.

Hopefully at all places.

Any idea how we can test this? That it is locked in all places and that
we didn't forget a place?

To be used when accessing the client lists.

And fix the tests. Some of them were broken a lot, some of them only
little.

To test the Mutexes, we'll need to run threads. So this is mostly to
support some tests for now, but it'll be needed later too.

Created with minimalistic set of functionality. Created a new library
for it, there'll be more thread-related stuff here.

distcheck failed since wasn't listed

okayed on jabber.

some stricter compilers require this.
this fixes a build failure: http://git.bind10.isc.org/~tester/builder/BIND10/20120829105133-Solaris10-sparc-Sunstudio/logs/build.out
okayed on jabber.

added some test cases to confirm the behavior; update the doc.

with notes about the intent.

hopefully the new name better represents the intent.

not sure if it's absolute necessary for doxygen to process it, but I thought
it's more readable anyway.

I forgot to add it before.

Obviously, it fails.