Hey Chuck, PEAR FAQ says:
> By implementing the base package exception interface, all exceptions for a given pear package can be caught with catch (\PEAR2\PackageName\Exception $e). But in PSR-11, there is only one (useful) exception interface: NotFoundException. Aknowledging the fact there is only one (and will be only one) useful exception interface for this package, does it still make sense to keep the base exception interface? David. Le mer. 17 août 2016 à 12:57, Chuck Burgess <demon.g...@gmail.com> a écrit : > PEAR most definitely wants to keep the package-level base exception, as it > is a convention we always expect to be available. We have *required* this > for years, originally as a class in PEAR1 standards, until we came up with > the idea of it instead being an interface while working on the PEAR2 > standards. We were quite happy with its demonstrated benefits, which > proved even better as an interface than a class [1], and were tickled to > see the use of it spread into the community after we published it. > > We would prefer to *not* lose the base exception interface requirement. > CRB > > [1] -- https://wiki.php.net/pear/rfc/pear2_exception_policy > > On Aug 15, 2016 7:35 PM, "Paul Jones" <pmjone...@gmail.com> wrote: > >> >> > On Aug 15, 2016, at 14:10, Matthieu Napoli <matth...@mnapoli.fr> wrote: >> > >> > Hi, > > >> > >> > PSR-11, aka ContainerInterface, has been sleeping for too long. Let's >> get that PSR moving! >> >> Woohoo! >> >> >> > Here is a change I would like to suggest: remove the interface >> ContainerException. >> ... >> > After years of using container-interop and ContainerInterface I have >> not seen a use case for that exception. We initially added it to represent >> any exception that could happen in a container. >> >> On principle alone, I usually like to see a package-specific base >> exception class, so that you can catch any/every exception from a >> particular package. (Maybe that's more an unnecessary consistency on my >> part.) >> >> >> -- >> >> Paul M. Jones >> http://paul-m-jones.com >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "PHP Framework Interoperability Group" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to php-fig+unsubscr...@googlegroups.com. > > >> To post to this group, send email to php-fig@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/php-fig/325BF45B-4638-43AA-9D6F-59BADB38C65E%40gmail.com >> . > > >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "PHP Framework Interoperability Group" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/php-fig/_vdn5nLuPBI/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > php-fig+unsubscr...@googlegroups.com. > To post to this group, send email to php-fig@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/php-fig/CANsgjnuZ%2B-MW1Avdu67RCqKQXkEA2YUSs%2BMrJqerRK3gXn6q%2BA%40mail.gmail.com > <https://groups.google.com/d/msgid/php-fig/CANsgjnuZ%2B-MW1Avdu67RCqKQXkEA2YUSs%2BMrJqerRK3gXn6q%2BA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CABAasbd7c4Z79jY0XDf3gDDG8JKu-h7ODeWggUkuP3kygqx-8Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
