Dear colleguas,
Dear Philip,
IMHO the best syntax will be a highly redundant syntax like (HT|X)ML:
For example:
<section transports>
<router A_smartest_of_routers>
option = value
...
</router A_smartest_of_routers>
</section transports>
Philip Hazel wrote:
PH> I don't want to go for a complete parser because Exim reads its
PH> configuration file very frequently. I want to keep the amount of
PH> work it has to do to an absolute minimum. So I don't want anything
PH> fancy.
This code can be parsed, validated and stored in "compiled" format by
some other utility, not Exim himself. The "compiled" format can be
totally machine-oriented. At present, I'm using 'cook' (a 'make'-like tool)
to manage my configs in "another" place (under my $HOME) and to copy
changed files to "system" location, sending a SIGHUP to exim when
neccessary. So the compilation step will not make any troubles -- just
one more line in 'cook' (or 'make') config. Include-d files (yes, I like
this feature" can be included by "compiler" and the correctness of
including will be verified that time.
Best regards and sorry for my poor English,
Dmitry
-- ---------------------------------------------------------------------
/"\ ASCII Ribbon Campaign
\ / - NO HTML/RTF in e-mail - NO Word docs in e-mail
X ------------------------------------------------------------------
/ \ [ Dmitry George Golub dgolub@??? ]
[ electronic mail system administrator +7(3422)917-324 ]
-----------------------------------------------------------------------
