Re: Splitting out ini setting per module like constants?

> > I cannot completely undestand what you cannot understand but you > > can easily spot what we have done with Friedhelm. Open eg. the > > reference.xml from the ibase extension. The new and clean structure > > for reference.xml files is the <section>-ed one you can see here. > > Every section has it's own id with EXTNAME.SECTIONTYPE format. Every > > section title is expressed by using a section title entity (to ease > > translation for lasy guys such as me :). The constants.xml file > > should be in the same dir, and look quite like the other <section>s > > in the reference.xml file (it could be easily modified from the > > copy-pasted sources from appendices/*). Then if you move the constants > > info from the appendices dir, the corresponding file should be deleted > > from there, and the entity from phpdoc/reserved.constants.xml should > > also be removed. > > Now that I've taken a look, I'm a bit confused. > > Ibase has cleaned out the cosntants in ibase/constants.xml , > ok. But they are not listed in reserved.constants.html in the > appendix. Wasn't it the idea to write down the constant one > time in the extensions directory but also provide a > comprehensive overview in the appendix? Yes but we will also need an autogenerator script, to autogenerate the constants index (to have it one place), much like the function index... Goba