Christopher Jones wrote:
Adam, can you:
1. Add this link to the RFC?:
https://wikis.oracle.com/display/mysql/Converting+to+MySQLi
Now that IS a good start!
Adding that to core documentation as well could be helpful?
But in a lot of cases it is the pre-loaded 'abstraction layer' that may be the
problem rather than the code for the site.
2. Mention how to turn off E_DEPRECATED warnings in the RFC?
But with a strong warning that on a later version of PHP things WILL stop
working altogether? More often now E_DEPRECATED is already switched off simply
to get PHP5.2 code to run so no one would see them anyway!
When users of 5.5 stumble on the new messages, we can then simply
point them to the RFC.
I think this is part of the problem. The material from the RFC's should be used
as a source to update the core documentation? Rather than another pile of notes.
IS the wiki intended to be a replacement for the core documentation? I've always
viewed it as a developers notepad for work that is in progress rather than
documentation itself, and once completed that material moves to the core manual?
In the case of removing any extension, good documentation is the key, and making
this more accessible to the 'general public', who in any case will probably
think 'PHP is ditching Mysql' what's going on ...
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
