Re: cf.data.pre solution needed

Agreed.

There is need for two changes:

1. Split the output in documentation and configuration. Having the
documentation inside the configurationfile looks nice at first, but in
the long run it is a very bad thing.

2. Include of option details, preferably from the relevant C files.

2b. Eventually the include concept should be extended to even have the
options included from the C files.

This change to include stuff is also required in the programmers guide.

/Henrik

Robert Collins wrote:
>
> Having done two 'plugin squid.conf' options - auth_param and filter_*, I see an issue cropping up:
>
> the cf.data.pre file becomes less and less useful: the modules have hardcoded parsing options rather than automagically generated
> entries in cf_parser.c. That's fine - for dynamically registering modules we have to have that. BUT the squid.conf autogenerated
> user doco runs the risk of rapidly going out of date.
>
> I am wondering whether having a cf.data.pre in each module directory that gets included (and only has DOC and NOCOMMENT sections) is
> a good solution,
>
> or perhaps an extended squid --help option where each module known to squid (compiled in || registered in the current squid.conf)
> gets a 'spit out doco' function called.
>
> Any thoughts?
>
> Rob
Received on Tue Jan 30 2001 - 17:52:24 MST