~samiam/MaraDNS

5480391fbd5c663eef671ddbed2f97bbdba2c0e3 — Sam Trenholme 13 days ago 7aa7cd9
Deadwood.ej: We allow leading whitespace in dwood3rc again

Ref: https://github.com/samboy/MaraDNS/issues/78
1 files changed, 7 insertions(+), 27 deletions(-)

M deadwood-github/doc/Deadwood.ej
M deadwood-github/doc/Deadwood.ej => deadwood-github/doc/Deadwood.ej +7 -27
@@ 62,36 62,16 @@ starting Deadwood) as the configuration file.

<h1>CONFIGURATION FILE FORMAT</h1>

The Deadwood configuration file is modeled after Python 2's syntax.  Any 
valid Deadwood configuration file should also correctly parse in both 
Python 2.4.3 and Python 2.6.6.  If any configuration file does correctly
parse in Deadwood but raises a syntax error in Python 2, this is a bug that
should be fixed.
The Deadwood configuration file is modeled after Python 2's syntax.  
However, since Deadwood 2 is no longer supported by the Python 
Software Foundation, and since Deadwood configuration files can sometimes
fail to parse in Python 3, Deadwood does not strictly follow Python 2
syntax.

<p>

Note that Deadwood configuration files are <i>not</i> always Python 3
compatible; while Python 2 is no longer officially supported, Deadwood
will retain its configuration file format.

<p>

This in mind, whitespace is significant; Deadwood parameters must be in
the leftmost column with no leading whitespace.  This is a valid line
(as long as there are no spaces to its left):

<pre>
recursive_acl = "127.0.0.1/16"
</pre>

The following line, however, will raise a parse error:

<pre>
 recursive_acl = "127.0.0.1/16"
</pre>

Observe the space to the left of the "recusive_acl" string in the incorrectly
formatted line.
In particular, leading whitespace is allowed in Deadwood configuration
files.

<h1>PARAMETER TYPES</h1>