Re: Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_default_classes.c zend_default_classes.h zend_execute.h zend_execute_API.c

From: Date: Mon, 16 Feb 2004 16:13:46 +0000
Subject: Re: Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_default_classes.c zend_default_classes.h zend_execute.h zend_execute_API.c
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-7882@lists.php.net to get a copy of this message
== Quote from Andi Gutmans (andi@zend.com)'s article > Marcus didn't mean it adds complexity to the code but to PHP. It's > obviously quite easy to implement this interface; implementation was never > a problem. > I don't really care too much if we have such an interface or not, although > I do think that it just makes things complex and I doubt almost anyone will > have a need for it. > I think the arguments given on this list for why we need this interface > were mainly academic and an attempt of people familiar with Java to copy > the hierarchy. The actual times you will need such an interface is quite > rare and I don't think it's worth the complexity for the one in a million > purist guy (i.e. people who want all their classes to inherit from a > CObject including exceptions). Implementing an interface would also help in getting round the very restrictive Exception implementation: * all methods are final, including getMessage() !!!, * its trace member is private. > P.S. - BTW, why not call it IException (or ExceptionInterface) instead of > Throwable? I think for people who don't know Java, it makes more sense. Why not, but in that case, the other PHP interfaces should also follow this naming convention. Stephane

« previous php.internals (#7882) next »