[Asterisk-Dev] generation of config files from source code ?

[Kaloyan Kovachev]

got it, but being lasy (too) I'd prefer to Alt+Tab (or Alt+F?) to the other
file instead of scrolling few hundred lines.
 I agree with Olle
> I think we should split up the sample configs into good examples and
> find a way to create reference configs with *all* config options, and
> call them "documentation". The configuration examples now are not very
> good examples any more. 
 it would be better to heave a 'jump start' config file and reference config
which in turn may point to the right comment label (say _conf_option_X_ ) in
the source - this way you get easy way to extend or change the option
explanation and it will be really few lines above in this case. Well in the
seccond case this is not a config file anymore, but documentation.
 

On Mon, 21 Nov 2005 00:34:30 -0800, Luigi Rizzo wrote
> On Mon, Nov 21, 2005 at 06:29:39AM -0200, Kaloyan Kovachev wrote:
> >  Having the config in the (right place in the) source file would also help to
> > find the option easier and to check what's going on and where it starts, but
> > there should be also a way to control the right location of _this_ 'comment
> > line' in the config file itself.
> >  The order of appearance of the lines in the config file and in the source
> > file is usually different, which could make a bigger mess instead of helping
> > to keep them in sync, I think
> 
> you should probably look at chan_oss.c because i am not talking
> about individual comment lines but an entire (and single comment) block
> in the source file describing the whole sample config file.
> 
> 	cheers
> 	luigi
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev