[squid-dev] Conf file syntax informative question.

[Amos Jeffries]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 4/11/2014 4:08 a.m., Eliezer Croitoru wrote:
> I know squid is here for a very long time and many enjoy it because
> of many things in it and one of them is the conf file syntax.
> 
> The conf file seems to prefer specific syntax and I am not sure
> about the reason for it. I do not have the knowledge to even try
> and dig here or there for discussions about the preference for the
> syntax else then the new ones.
> 
> I must say that the logic at least for me makes sense and this is 
> probably because I have learned to use this logic before touching 
> other things and it seems to me that there is much more
> background. I am wondering where to start reading at the mailing
> list or If there is some written article that you know about the
> subject that can help me make some sense into the syntax choice.
> 

I dont think its documented anywhere in particular. AFAIK its one of
those emergent properties that has come about. There are at least 3
distinct parsers involved with processing it today.

In abstract it is something similar to this:


line := empty | [ directive fields ] '#' comment

empty := [CR] LF

comment := .* LF

directive := component '_' item

fields := field [fields] [options]

field := option | option-value

options := option [options]

option := name [ '=' option-value ]


Amos
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUWDT4AAoJELJo5wb/XPRj64MIALzSVltaTrWlUcYflBBhBLc9
B50dcIUWjkslXfS11EpFsbuDzrwOOlPzMwBLJIDZNAPXsivsxsYY2GXBMLHnRqf0
jSl2v42HUry9I8HfQ9zUzOy/gxsusBvZ+i76APej+tHg+19DYCXHXXLb5RsiUWQ8
7L4J9gtrDB1hsDVz01XGAHrxSZF2vzYJAIIU9MOQgS6Q1qt8QVJvYAfkFOkKasGU
YdSw5eW0BXfIRYZBa6VwIezX31K2VisERaASGIeLF6aDEclW/mFkFwCpugF6o6hi
PTo3W4Ce7X6aUu1QtqB5i5n8fQRGdzTGtv1SVaUAvpKVAiBu9scwAurrRlGjCp8=
=EzC8
-----END PGP SIGNATURE-----