... fixing a warning.  The addresses are the same,
but it wasn't completely correct.

... fixing a warning.  The addresses are the same,
but it wasn't completely correct.

Move the version to 1.2.0-dev

Just marking this as 1.2.0-dev

See merge request !98

layer/rrcache: ds cache rank was fixed

See merge request !95

news: mention the most important stuff since 1.1.1

In future I hope we'll be adding these items at once with the features.

See merge request !94

In future I hope we'll be adding these items at once with the features.

and fixup with DEBUG -> VERBOSE renames.

As requested in !90, I have renamed all *_debug_* and *DEBUG* to verbose
(where it made sense), and renamed NLOGDEBUG to NOVERBOSELOG.

The logic is simple - most usually we want to have verbose logging
compiled in and `assert()` not compiled in (`-DNDEBUG`).

Now that we renamed "debug" to "verbose", the old name didn't seem very
suitable anymore; this new identifier haven't got to master yet.

Split NDEBUG to NDEBUG (asserts) and NOVERBOSELOG (verbose logging); rename all related symbols to use VERBOSE instead of DEBUG

... but don't raise any kind of error.
The lua function `verbose()` behaved reasonably already.
It doesn't warn, but docs for the function do mention `NLOGDEBUG`.

In particular, don't require to call an externally defined function to
find if in --verbose mode or not.  Now it's just an extern bool.
I'm confident the performance impact of not using -DNLOGDEBUG should be
negligible now.

This comes with a small incompatible API+ABI change, but that shouldn't
matter as we've had a couple of those already since the last release.

This reverts commit 64f80706.
TL;DR: it brought almost no benefits AFAIK and potential for problems.

See commits for details.

layer/pktcache: additional checking for cache entry rank was added

See merge request !86

Fixes https://github.com/CZ-NIC/knot-resolver/issues/35.

This reverts commit 64f80706.
TL;DR: it brought almost no benefits AFAIK and potential for problems.

The "portable bytecode" produced by luajit isn't compatible when
(lib)luajit version changes or when some build-time configuration of it
changes.  If you mix these up, kresd fails to start.

Fixes #111.

Compatibility: it needs a new libkres.so function.  If a wrong version
combination is attempted, the module just cleanly fails to load, though
it writes a slightly confusing message "no such file or directory".