INN config file parsing infrastructure
rra at stanford.edu
Thu May 4 23:36:49 UTC 2000
Bill Davidsen <davidsen at tmr.com> writes:
> The use of the # comment character should be clearly defined. My thought
> is that it should introduce a comment to end of line whenever it is
> found unescaped and unquoted. But if people really want it only as the
> first character of a line the spec should say so.
I managed to leave out comments in the original spec completely. Sorry
A comment is introduced with the # character and extends to the end of the
line. A comment is valid anywhere except within a quoted string, where
the # will be treated as a normal character.
I agree with the idea of making the syntax writeable as well as readable
by a program, and I agree that traditional comments don't have much role
in that sort of setup, but I'd rather fully support traditional comments
for the first pass and then go back and add a semantic comment mechanism
later (as the comments aren't *necessary* in machine-generated config
files, just helpful).
Russ Allbery (rra at stanford.edu) <http://www.eyrie.org/~eagle/>
More information about the inn-workers