Hi Timm, On Sun, 15 Feb 2004 12:53:21 +0100, Timm Friebe wrote: > As of B4, this is no longer possible. That's why i was agreeing to > Sterling in saying it should be optional to use the built-in exception > class. If there was a requirement to implement an interface (call it > Throwable, for instance), simply let the built-in class implement it. > People wouldn't have to get into interfaces when using (and/or > subclassing) it but *only* for the case when they want something > similar to what I described above. People wanting this will tend to be > the kind of people that know about interfaces, anyway:) First of all, I think there must be a "catch all" method for exceptions. This can be implemented by forcing a "base class", using an "interface" or a language construct. IMHO, as you said, using an interface and letting the built-in class implement it is the best approach. But only instances of classes wich implement this interface should be throw or caught(language enforcement). With this enforcement, we can have a "catch all" for exceptions with less pain.
Cristiano Duarte -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
