== Quote from Derick Rethans ([EMAIL PROTECTED])'s article > On Tue, 17 Feb 2004, Stanislav Malyshev wrote: > > > >> >Again, I don't see any complexity arising from this: The average user > > >> >would simply use "catch (IException $e)" instead of "catch (Exception > > > > That looks weird. Why IException? Ah, because it's an interface. And > > what's an interface? And why should I know about interfaces if > > I just want to catch damn exceptions and that's all? > > > > Simple stuff should be simple. If you want to catch exception, you > > shouldn't go and learn how interfaces work in PHP and what are the > > inheritance rules and ton of other stuff. You should just do > > catch(Exception $e) and that's it. > > Right, can't agree more with this. > > Derick
The problem is not the name, but the fact that some people would like to have an interface as the exception base hierarchy. "Throwable" was first proposed, but some people considered it was too Java oriented. We could also have this interface named "Exception" and the PHP class implementation "PhpException" .... Personally I don't like interfaces start with an 'I'. I would also prefer "Error" instead of "Exception" because I consider what we get is an error, exception is just the mechanism to report errors. Stephane -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
