Hi Marcus, On Sun, 15 Feb 2004 16:12:08 +0100, Marcus Boerger wrote: > Even if it were not the best solution it is still the solution that fits > PHP best and which is easiest to the developers. And as i said a while > back the current exception class allows several things a user > implementation cannot do. Though meanwhile some of those things are > possible in userland too there is still the 'rock solid' argument - the > worst thing that could happen is an unstable or uncontrollable exception > base implmentation and even worse is if there is no such base at all > (the interface or real catch all approach). Do you really think that enforcing an interface will lead to unstable code?
As Timm said, if the internal Exception class implements it, the newbie user can use it without knowing that it implements "the interface". But if you need to make your own interface hierarchy, just let your base class implement "the interface". IMHO, we need to have a "catch all", so just enforce the implementation of "the interface" by classes in throw/catch statements and that's it. BTW, thanks @internals and specially you, for helping me last year. You guys are really great and if my PHP5 CORBA extension is becoming real it's because of you. Cristiano Duarte. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
