INN config file parsing infrastructure

[Marco d'Itri]

On May 01, Russ Allbery <rra at stanford.edu> wrote:

 >> I think this is confusing. This behaviour is very non intuitive, when
 >> UNIX programs implement \-escaping the \\n sequence is usually special
 >> cased.
 >
 >This is a good point.  On the other hand, I really don't want to get into
 >handling the full set of C backslash sequences, at least for right now
 >until we have some pressing need for them.  INN doesn't really need the
 >ability to embed newlines in a string; shall we just say that escaped
 >newlines disappear completely like they do in C?
I think this is a good compromise. The syntax you proposed is very
C-like, so using \ for line continuation is IMHO the natural thing.

I vote for "include" instead of "%include".

-- 
ciao,
Marco