Re: Mail_IMAP 2.0.0 alpha 1

Lukas Smith wrote:

Exactly because there are different developers involved in those n-layers I am concerned about the implications of Exceptions.

This is easily solved with api documentation.

In my world, PHP applications are becoming far more complex and multi-layered. I see this everywhere I look, with frameworks obtaining new levels of stability & quality. I see the introduction of Exception as tribute to this new demand for PHP. Indeed Exceptions are not particularly well suited for building flat, quick PHP scripts. They exist for complex OO architectures. PHP5 in general exists for complex OO "enterprise" applications.

I can see myself using Exceptions inside my application logic much more than inside a general purpose libary I choose to use.

I think it's just as valid for both. You can repackage the low-level exceptions as application exceptions too. (See the wiki for more on warpping and exception types.) Using exceptions for low-level packages and application logic adds a coherence to your system that would otherwise be missing. Plus the boundaries of application vs. low-level library can be rather nebulous. Hans