Subject: [htdig3-dev] Re: Validation of .conf files. (3.20b2) (PR#948)
From: Gilles Detillieux (firstname.lastname@example.org)
Date: Fri Nov 17 2000 - 13:31:20 PST
According to Sphboc@aol.com:
> Appears to me that it "might be" useful to develop logic to validate a single
> ".conf" file, and/or especially the set of all .conf files which participate
> in a given run.
> Types of errors/warnings possibly including:
> A. Syntax violations.
> B. Use of undefined variables.
> C. Definition of never-used variables.
> D. Attempts to include non-existent files.
> E. Include loops; A includes B, and B directly/indirectly includes A.
> F. (Possibly) warnings due to use of unreliable and/or deprecated features.
> I'd see this as a module which would be invoked by calling it with either the
> name, or the content, of a .conf. Output would include both a return code,
> and error diagnostics.
> Has there been any discussion of this? Was thinking that, if it "sounds like
> a good idea" but no work on it is active, I might try my hand at developing a
There hasn't been any discussion of it that I can recall. The only
thing that came close was a suggestion requiring explicit declaration
of any attribute names you make up yourself, and then having the config
file reader flag any unknown attribute name to catch typos. No one is
working on that either, though. This should probably be discussed on
the htdig3-dev list. If you're keen to work on this, I certainly won't
hold you back.
-- Gilles R. Detillieux E-mail: <email@example.com> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil Dept. Physiology, U. of Manitoba Phone: (204)789-3766 Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------ To unsubscribe from the htdig3-dev mailing list, send a message to firstname.lastname@example.org You will receive a message to confirm this.
This archive was generated by hypermail 2b28 : Fri Nov 17 2000 - 13:39:05 PST