On Fri, 7 Dec 2001, Matthew J Gray wrote:
> bind() takes the name of a class and the name of a function and > "binds" the function to the given class. This is useful to us when > the interface class of a library is a subclass of another class in the > library. > > bind() doesn't quite work properly, but multi_extend does and I plan > on adding it to the machines in our test environment. Long term, > however, it would be nice if this sort of multiple inheritance > functionality was part of php so it could be better maintained and > developed in more competent hands. > Be careful with the function names, as bind() is already being used by the sockets extension. See: http://www.php.net/manual/en/function.bind.php I believe the new sockets extension names it socket_bind(), but anyway.. > I am wondering: > 1) Are we alone in wanting this sort of functionality? Would anybody > else find this useful? > 2) Could it be better implemented in php using keywords(extends taking > a list of parent classes) and operators(::) ? > 3) Why overloaded classes? It doesn't seem very straight forward from > a usuability standpoint(maybe I am biased since I has such bad > experience getting __sleep and __awake to work and would rather never > use a __* method again). > No, you are not alone wanting this sort of functionality. Other people probably want this as well, but the real problem now is that Zend 2 is being written and an extension doing this now would be kind of awkward. I mean, if people start using this new extension with PHP4 and then later on have to use PHP5 which already has multiple inheritance 'built-in', the syntax would be different. You probably can imagine the backwards compatibility problems this could cause. Cheers, Joao -- Joćo Prado Maia <[EMAIL PROTECTED]> http://phpbrasil.com - php com um jeitinho brasileiro -- Precisando de consultoria em desenvolvimento para a Internet ? Impleo.net - http://impleo.net/?lang=br -- 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]
