[wp-hackers] PHP5 and WP Development

[Tor Bjornrud]

On Aug 12, 2004, at 8:26 AM, Dougal Campbell wrote:

> Tor Bjornrud wrote:
> > [...]
>> If the decision is made to let php5 code in, it means maintaining two 
>> codebases, either by version detection or branching of the cvs.  What 
>> I'm trying to determine is if we're postponing these changes due to 
>> immaturity of the new libraries or lack of php5 acceptance to end 
>> users... all valid reasons.  Alternatively, will we immediately fork 
>> the code and maintain different trees to save on package size of 
>> files or maintain it all in one tree with version detection, giving 
>> those who do run php5 a better product?
>
> Actually, there's a simpler path for some of that. Most of the 
> database access is already isolated. It wouldn't be all that hard to 
> detect which  version of PHP was running, and import "wp-db4.php" or 
> "wp-db5.php", as appropriate. The database class is pretty static, so 
> once the mysqli version is written, it shouldn't be much work to 
> maintain the two parallel versions.

Yes, that's exactly what I meant by "all in one tree with version 
detection" as opposed to different cvs branches.