This is useful for shell script wrappers that can take the original
command as an argument as well as the %{o,s,w} expansions as additional
parameters.

This way the documentation can show neutral defaults for parameters that
are highly platform-dependent.

Similar to PLATFORM_DEPENDENT for things affected by configure options
or other build flags that are not necessarily linked to the target
platform.

With a new %w expansion in the cc_command parameter.

But inject it back into OCFLAGS for distcheck continuity.

And expose bereq.time in vcl_pipe now that we have some.

Refs #3562

fickle for that, and misleading information wastes oceans of time.

They are grouped by categories and that hasn't changed, and the order
of groups haven't changed. All occurrences of foo.* variables are sorted
alphabetically instead of approximately by relationship between each
other.

Inside the first group, variables are now ordered based on the PROXY
protocol diagram:

- client
- server
- remote
- local

A note was added and is hopefully visible enough to maintain this order.

You can verify that nothing changed:

    $ COMMIT=<this-commit-hash>
    $ git show $COMMIT~:doc/sphinx/reference/vcl_var.rst |
      sed '/^$/d' |
      sort |
      sha1sum
    3400130e88c0456b3bc779b9dfeeff09e130efa3
    $ git show ${COMMIT}:doc/sphinx/reference/vcl_var.rst |
      sed '/^$/d ; /.. NOTE:/d' |
      sort |
      sha1sum
    3400130e88c0456b3bc779b9dfeeff09e130efa3

Use whatever alternative to sha1sum your system may provide.

This reverts commit 82be6f46.

I checked the git history to understand this comment.

And complain when two parameters are passed instead of one parameter and
one option.

Confusing panic output was generated when a worker ran multiple
requests before returning to the pool.

Noticed when debugging #3755 :

  VCL::methods = {RECV, PASS, HASH, MISS, HIT, DELIVER},

Same panic with this fix:

  VCL::methods = {RECV, HASH},

Fixes #3755

I have checked that this catches #3752 too

This is useful to ensure that workspace does not, by chance or
accident, contain data and, in particular, magic numbers from
previous workspace use.

With this change, we can formalize the renaming of a parameter while
maintaining the old name temporarily for compatibility.

A deprecated alias can be set with either param.set or the -p option,
but won't be listed by:

- param.show [-j]
- param.show [-j] changed
- param.show -l

Only an explicit param.show for the name of the alias will provide a
minimal documentation with a deprecation notice and the current value.
In the manual, there is only a deprecation notice. The rationale is
that administration tools shouldn't pick them up when enumerating the
parameters.

Since we currently don't have deprecated parameters, this can only be
tested manually, for example:

    PARAM_ALIAS(vcl_dir, vcl_path)

To ensure that we don't break this, we could consider having a perpetual
deprecated parameter.

Fixes #3752

This reuses the stringform concept and introduces a similar bodyform
flag for STRINGS and BLOB types. We can now assign either a STRING or
a BLOB to [be]resp.body, without breaking the VRT ABI and API. In fact,
the VRT API now uses a void* C type for the BODY VCL type and finds
which type to use based on enum lbody_e.

The enum completely changed but macros were added to maintain the API,
and because of this change, enum lbody_e literals are formatted in two
steps. As a result the BODY type grew another noindent flag. It prevents
the insertion of white space between the LBODY_{ADD,SET}_ prefix and the
type name suffix (BLOB or STRANDS).

This way they can all nicely align in the VTC output.

The recently added "end" legend that denotes the end of a transaction
before a match happened for the given VXID conflicted with the end of
the logexpect spec. The latter was renamed to "done".