Great Circle Associates Majordomo-Workers
(April 1996)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: Config file commentary.
From: Dave Barr <barr @ math . psu . edu>
Date: Tue, 23 Apr 1996 11:37:50 -0400
To: majordomo-workers @ GreatCircle . COM
In-reply-to: Your message of "Tue, 23 Apr 1996 15:04:37 +0200." <199604231304.PAA29861@slurp.neu.sgi.com>
References: <199604231304.PAA29861@slurp.neu.sgi.com>

In message <199604231304.PAA29861@slurp.neu.sgi.com>, Chan Wilson writes:
>What I'm proposing to do is have the list config file be a pure list of
>
>     variable = value
>
>with *no* commentary.

Yes, this is probably a good idea.  I've pondered this several times too.

It would save some CPU time in parsing the files, which is always a
good thing.  Perhaps it would be a good time to experiment on more
parsing-efficient methods of storing the "internal" version of the
config file?

For a transition you could have a comment-detector put in the parser
which would call a "decommentify" routine and rewrite the config file
on disk whenever it encounters an "old-style" config file.  It could
also even detect missing variables and insert defaults (even notify
owner of the new variables so she can confirm their values?)

--Dave




References:
Indexed By Date Previous: Re: Security Flaw in Majordomo (fwd)
From: Chan Wilson <cwilson@slurp.neu.sgi.com>
Next: Re: Config file commentary.
From: Dave Wolfe <dwolfe@risc.sps.mot.com>
Indexed By Thread Previous: Config file commentary.
From: Chan Wilson <cwilson@slurp.neu.sgi.com>
Next: Re: Config file commentary.
From: Dave Wolfe <dwolfe@risc.sps.mot.com>

Google
 
Search Internet Search www.greatcircle.com