INN config file parsing infrastructure
tco2 at cornell.edu
Fri May 5 16:19:23 UTC 2000
Piecing together several of your comments on the whitespace & \<newline>
issue, it seems to me that there is a problem ... but I could just still
be confused ....
If I understand correctly the spec would say:
1) (correct) parameter: token
2) (correct) parameter: "token1 token2"
3)(incorrect) parameter: token1 token2
4) (correct) parameter: "token1 \
5)(incorrect) parameter: "token1
Further, in #4 the \<newline> is retained in the parsed result,
rather than being elided. (eg #4 produces the string
"token1 \n token2"
Thus there is no provision for the sort of thing we can currently do in
And there is no provision for line breaking a "string" in the config file
without having that line break be embedded in the value that is extracted.
If this is correct then I see two problems ... one practical (and maybe trivial)
and one more principle based.
More information about the inn-workers