The important thing is to keep at least the same level of functionality for procedural coding
This was the entire concern raised about too much OOP form what I gather. There was also the concern raised that your design will be heavily influenced by the possibilities offered by the ZE1, where as the ZE2 will allow many new things that will result in a very different design. Also I do not like how different the API's are in some respects as it is. Further diverging them is nit helping imho. People that want an OOP interface can choose one of the major DB abstraction layers (PEAR DB, Metabase, ADODB ...). Then again Zak's proposal is not about abstraction but about giving an OOP interface and if you are going to do it anyways I guess we can postpone the discussion until the code is there :-) Best regards, Lukas Smith [EMAIL PROTECTED] _______________________________ DybNet Internet Solutions GbR Alt Moabit 89 10559 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de [EMAIL PROTECTED] _______________________________ -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
