GitLab

Obviously, it fails.

Mostly by jinmei, small changes by vorner (assert->throw, as assert can
be turned off).

okayed on jabber

this fixes build failure reported at:
http://git.bind10.isc.org/~tester/builder//BIND10/20120825015000-Solaris10-sparc-Sunstudio/logs/build.out

this sometimes happens, and depending on the environment, what() isn't
always displayed.  so it's helpful to catch it and report the error.

not directly related, but would be useful for extending the benchmark
code and to check the server behavioer.

also clarified RdataEncodeSpec is a forward delcaration (maybe obvious,
but the sudden single declaration looked a bit awkward)

and, make class-vs-struct consistent for it; clang++ requires the consistency.

* Check for impossible return value and throw in that case.
* Call nextInternal directly, to avoid some indirection. This might
  cause a small performance benefit.

They share some bit of private stuff, so we get rid of the private
header. We still have a bit of the code included from outside, but this
is only for tests (and it's not a header).

using EXPECT_EQ(==) instead.

the experimental instrumental reader implementation is now removed.

- spacing
- const
- type clarification
- postion of ++
- indentation
- comment wording

added a test case for it and updated the doc.
rbtree/domaintree was modified to avoid such operations.

As we want to make the impression the data is opaque, should not be
examined or pointed into the middle of it.

my compiler even checks assignment-only variables, apparently

During the removal of the interface, a test with rewind was removed.
Adding a new one instead.

After the removal of one interface.

Also, fixing a small bug for it.

The return value of next() tells only what boundary it is now (between
Rdatas, in the middle of one rdata, or completely at the end).

As a side effect, it now can detect end of single rdata.

Part of the tests were dropped, as they make no sense. Others were
adapted. Some more will come.

Also, documentation was not yet updated.

       from config_unittest.cc

This will be useful in debugging the OpenBSD setsockopt() failures.

- add zone and file names to masterload errors
- catch masterload error and log it
- don't quit auth completely on a single zone load failure