On Feb 7, 2013, at 5:36 PM, Hannes Magnusson wrote: > On Mon, Feb 4, 2013 at 12:34 AM, Philip Olson <phi...@roshambo.org> wrote: > >> >> As for what to do, I recommend: >> >> a) We add <methodsynopsis> to all SPL aliases >> b) Be certain that every "Class synopsis" page is accurate > > So this came up the other day when someone filed a bug report about > not finding php.net/_ . > This fix was to manually hack it into the search iirc. > > I'm pretty sure the real fix to all aliases as methodsynopsis. They > would then be listed automatically correctly, pointing to their > parents page, and would be indexed by PhD.
I'm not sure what you mean. Do you mean adding an XML file for every alias? For all aliases? Like the permanent ones (_.xml), deprecated ones (mysql-dbname.xml), and those that have been removed? Or maybe you mean (d) from the previous email? > I have no idea why this was not allowed in the past? I think because it'd mean adding hundreds of files to the manual, mostly for old/deprecated aliases that nobody really uses. And then maintaining them. And then having them clutter the documentation TOC/navigation. Granted we could create QA tools and make changes to how it's rendered, but I think that's why we don't do it today. > These random inline notes, and dedicated page for aliases listing > seems like a total wtf to me. I'm not sure what this means. Which inline notes? And I do not think a page listing aliases is a WTF but maybe I am missing the meaning. Do you mean WTF because it's so outdated? Regards, Philip
