long long) agnostic.

into nitpicking mode, so the test-cases reveal if the VCC outputs
anything bogus or suspect.

find out how that can work.

Make min/max values strings, and test-convert them along with the
default value during startup, to see that we can.  At the same time
normalize the strings with the parameters tweak function.

List min/max values in .rst doc.

param.show will flag default values. (Better the other way around ?)

Add a new feature:

	param.show changed

will only list parameters with non-default values (in short format)

various pointless malloc'ing.

VSB instead.

run-time determined defaults.

Certain of our parameter names are so long that they have shoved the
"long" param.show output all the way to the right.  Break the line
after the param name and use most of the width again.

Also add support for two column tables using TAB chars, for descriptions
of params like "debug", "feature" etc.  The width autosizes, and lines
wrap as expected in the second column.  Eliminate the 'pad' field in
the tbl includes.

Move all the "tweak" functions to a separate source file.

Clean up white-space in param descriptions.

when -i is given.

This allows the testcases to be written:
	import ${vmod_directors};

Add a feature for ${topbuild} and test it in the remaining to tests
which use ${topbuild}.  I don't see any obvious way to write those
two cases without needing ${topbuild}.

I belive we are now very close to being able to run our testcases
out of tree.

Define a macro for all programs, so they can be overwritten from
the command line.

Change '-i' to mean "You're in a source tree":

	Find top of build-tree by reading Makefile

	Set $PATH which can find all programs

This picks a random port number, possibly two, one for IPv4 and one for
IPv6, and varnishadm() can find those in VSM.

went into.

Reflect this change in varnishtest, and retire the "-storage"
keyword, storage settings can now be done with -arg.

not annoy FlexeLint.

If you specify no -S file, one will be made for you.

If you truly want no authentication of CLI connections, give an
empty -S argument  (-S "") and live with the warning that causes.

Use arc4random() for challenges and secrets, we want crypto strength.

is always synchronized with obj->len.