Re: MySQLi

> Ok, that was some kind of misinformation then. In other words, let's add to > manual.xml.in. After I do the work on at least reference.xml, I agree with Phillip that it should have some installation docs, etc. first at the very minimum. > No, take a look of ncurses. People used it, when there were only protos > available. I started to document some functions, and "new" people, developers > and php-doc people contributed documentation too. It was never complete or > had complete information. We should also cover extensions which are > experimental, and which aren't ready neither in code or documentation. Well I've documented most of MySQLi already in terms of functions. My plans are to get the reference.xml and friends stuff sorted out (at which point I see no reason not to include it in the standard doc build), and then finish up the other functions descriptions. After all of that is done, then I'll start adding examples, etc. > PHP-Documentation is not a book for a final version, it should cover also new > ext's. And how people which aren't involved in dev or doc should know, that > there is a new extension available? Unless Phillip has some reason other than that which he already expressed, it'll be in the book by Monday. > It works fine, but it depends on your configuration. If you decide to use the > bundled lib with 4.1 server, you will run into several authentication > problems of course. Even so, that's something that needs to be documented. > I don't see a BC problem - we have the same problem with two oracle > extensions, which aren't compatible. The ext/mysql supports an optional last > parameter, which is a link - this makes it nearly impossible to support > future releases of libmysql which added additional parameters to functions. > If people don't need MySQL's fast and powerful api-features which were > implemented in version 4.1, they still can use ext/mysql without any BC > problems. Changing ext/mysql to support MySQL 4.1 api would break BC. From my perspective we should really just focus on what needs to be done to get mysqli doc'd and the docs for ext/mysql updated as necessary. Unless someone wants to stand up against it I'll continue on with the plan of doing reference.xml properly and then putting mysqli back into the doc build. Regards, John -- -~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~- John Coggeshall john at coggeshall dot org http://www.coggeshall.org/ -~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~-