On Mon, 03 Feb 2003, Harald Radi wrote: > that would be a big step back again for several reasons: > > -) if done in c code you have one function serving as function and method, > thus you have the same order/amount of arguments for the function _and_ the > method.
I don't see this as an issue - the OO API in PEAR would be a simple wrapper for the function. > -) if something changes in the code, it automatically changes for the function > and the method, if we had a pear class someone would have to maintain that. See above. > -) we finally brought down the cost of handling object beeing virtually the > same as for handling resources, so why should we try that hard to make the > damn thing slow again ? You are proving my point - the cost of handling objects is minimal, so why not do it in userland? > -) the errorhandling issue is not (easily) coverable if we simple wrap the > funcitons as pear classes. What errorhandling issue? -Andrei http://www.gravitonic.com/ * Quantum Mechanics: The Dreams of Which Stuff is Made. * -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
