For now we assemble the string in the worker threads workspace.

I will reintroduce the optimization to pass it to VRT uncollected
where appropriate, once I get the new expression system pushed through.

Add a hacked up "regsub" function call for now, once functions gets
introduced it should be treated like any other function.

Add "true", "false" BOOL constants, REAL constants

Move the "set" statement over to the new expressions.

Fix testcases to use new string concat syntax where applicable.

"set req.url = 1;" was impossible before, now it works.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5131 d4fa192b-c00b-0410-8231-f00ffab90ce4

the way we learned to do it back in the 1950'ies.

Until now, VCC has used sort of a massaged C-expression and with
the introduction of things like regexp matching and ACLs that turned
sort of ugly.

This code is classic recursive expression parsing with a couple of
twists:

1. We don't build a tree, because we are not going to optimize stuff,
   we leave that to the C compiler.

2. Instead of the tree we build a string with magic markers that
   let us get the indentation of the produced C code right anyway.

3. We do type-hinted parsing, in an attempt to produce intelligent
   error messages and sensible semantics.

This code passes all testcases with a single change:  We can now
compile "if (2 == 3)".  This is probably a good thing (?)

Beware of bugs...




git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5130 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5129 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5128 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5127 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5126 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5125 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5124 d4fa192b-c00b-0410-8231-f00ffab90ce4

two (IPv4/6) available sockets.  In this case, writing the :0 into
the VSM will not tell varnishadm where to look.

Write the actual socket addresses, one per line instead, and have
varnishadm try them all.

Make -n mutually exclusive with -S and -T on varnishadm.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5123 d4fa192b-c00b-0410-8231-f00ffab90ce4

as a socketaddr.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5122 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5121 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5120 d4fa192b-c00b-0410-8231-f00ffab90ce4

	IP# <space> PORT#

Explain why.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5119 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5118 d4fa192b-c00b-0410-8231-f00ffab90ce4

as a default, if the host argument does not specify a port.

Elminate most separate calls to VSS_parse()

Make it possible to specify address and port of backends in VCL using
only the .host field.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5117 d4fa192b-c00b-0410-8231-f00ffab90ce4

have to kill the child:  We cannot get the CLI pipes back in sync,
even if the child process was just preoccupied with something for 
much longer than cli_timeout.

Fixes: #744



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5116 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5115 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5114 d4fa192b-c00b-0410-8231-f00ffab90ce4

Fixes: #758



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5113 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5112 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5111 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5110 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5108 d4fa192b-c00b-0410-8231-f00ffab90ce4

Usage: cd bin/varnishtest/; make -f Makefile.kristian -j20



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5107 d4fa192b-c00b-0410-8231-f00ffab90ce4

The embedded dot claimed obj.* was available in vcl_fetch, something
it's not.  Fix this.

Thanks to Yves Hwang for spotting this.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5106 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5105 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5104 d4fa192b-c00b-0410-8231-f00ffab90ce4

Spotted by: pprocacci  (Thanks!)

Fixes: #752



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5103 d4fa192b-c00b-0410-8231-f00ffab90ce4

the transfer failed before we received anything.

Fixes: #749



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5102 d4fa192b-c00b-0410-8231-f00ffab90ce4

value that indicates if a failure should be retried.

Condition for retry is that the connection is recycled and fails before
we receive any data from the other end.

(The actual retry is not implemented yet)




git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5101 d4fa192b-c00b-0410-8231-f00ffab90ce4

Fixes: #741



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5100 d4fa192b-c00b-0410-8231-f00ffab90ce4

Whitespace nits



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5099 d4fa192b-c00b-0410-8231-f00ffab90ce4

FlexeLint spammage.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5098 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5097 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5096 d4fa192b-c00b-0410-8231-f00ffab90ce4

Add cheesy display of same in varnishstat curses mode:

          16         0.00         1.00 uptime - Client uptime
           1          .            .   VBE.fs(192.168.60.20,,80).vcls - VCL references
  0000000000 <____VVVVVVVVVVVVVVVVVVVV VBE.fs(192.168.60.20,,80).happy - Happy health probes
  top bits    bottom bits one-by-one

We need to start thinking about how to structure varnishstat output...


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5095 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5094 d4fa192b-c00b-0410-8231-f00ffab90ce4

make it work again to the point where all test-cases pass.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5093 d4fa192b-c00b-0410-8231-f00ffab90ce4

decided naming/identity scheme.

Now I just need to get probing working again, will say when it works,
right now s00002.vtc plus likely others fail.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5092 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5091 d4fa192b-c00b-0410-8231-f00ffab90ce4