Generating loadparm from our XML documentation
obnox at samba.org
Thu Jan 9 10:20:13 MST 2014
On 2014-01-10 at 00:02 +1300, Andrew Bartlett wrote:
> On Thu, 2014-01-09 at 08:28 +0100, Volker Lendecke wrote:
> > On Thu, Jan 09, 2014 at 12:24:14PM +1300, Andrew Bartlett wrote:
> > > On Wed, 2014-01-08 at 11:13 +0100, Volker Lendecke wrote:
> > > > On Tue, Jan 07, 2014 at 04:34:41PM +1300, Garming Sam wrote:
> > > > > I've just put all the changes into a repository as the patch was too
> > > > > big for the list.
> > > > >
> > > > > git://git.catalyst.net.nz/samba.git rename-param
> > > >
> > > > I agree that the names do not follow Samba's variable naming
> > > > convention, but just doing a sweeping change is questionable
> > > > at best: It will cause pain for people who have to port back
> > > > and forth patches for no good functional reason, they don't
> > > > even clean up convoluted code.
> > >
> > > > Can you please explain why you need to rename all the
> > > > parameters?
> > >
> > > The future step of auto-generation requires this, as otherwise each of
> > > these variable names would need to be encoded into our XML
> > > documentation, which would increase the risk of errors being introduced
> > > at that step. While not perfectly consistent, the current _-separated
> > > names generally match the parameter string.
> > It does. However -- can we discuss how you envision the
> > parameters to be handled in the future? The current
> > situation is a mess at best, and before we go too far into
> > one direction, I would love to see consensus how to do this
> > in the future. You seem to indicate to generate code from
> > XML? Wouldn't it be better to generate the XML from code?
> > This would make XML handling optional for people who *just*
> > want the code and don't care about manpages.
> I'm very happy to discuss this, which is why I've tried to foreshadow
> where I hope Garming's work might go since the first patches sent on
> Christmas Eve.
> First, the fundamental idea (of generating this all from the docs) isn't
> mine, or particularly new. I'm pretty sure Michael Adam was the one to
> suggest it to me during one of the previous re-factoring stages. We
> discussed it as a long-term goal in
> and I also mentioned it in October when we fleshed out lib/param/README
> with aca475b6bcbe364d09b83d17bf0504741ed3a84a.
We certainly discussed this more than once, and I definitely
said I would love to introduce once central place to store
all information about a parameter, and generate all and doc
from that. I would even be surprised if anyone would
But I definitely never suggested to generate code from the xml
docs. Instead, what I suggested at the time is to have one
central python program to generate all code and the xml doc
sources for the parameters from python data structures.
In principle the effect is the same of course.
And I consent that using an existing standard parser
for extracting the information from xml and then generating
the code from there might have advantages over self-written(?)
code that generates xml doc from python data.
Still, I think I'd like the latter better.
(But that is just a detail... :-)
My main critique now (just like 2+ years ago) is that I think
that we should first refactor the two separate loadparm instances
to the point that they are the same and can be moved to the base
dir completely. And then start generating this. We should not
start to add generating code for the convoluted state we
That being said, regarding the currently prosed patchset of
renaming lots of variables: Is this really necessary right now?
Can't it be held off until we really do the autogenerating bit,
even more if the patches are more or less automatically
There are also quite some changes of defaults.
These have to be reviewed and tested very, very carefully, imho.
I have to look more deeply into the patches and the last mails,
but wanted to give a pong to indicated that I am also interested
in this and thinking about it, before leaving office... :-)
Cheers - Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 215 bytes
Desc: Digital signature
More information about the samba-technical