Looks like a step backwards to me. In fact, I just had issues with code (in zendframework https://github.com/zendframework/zend-servicemanager/pull/167) that assumed integer error codes, but then failed because PDO failed to adhere to the property specification (PDO needs fixing here, not the other way around!).
If you allow anything in there, we'll just have more issues in consumer libraries that have this assumption and consume exceptions (all of them, if they are done correctly), since you just broke invariance. If you really need to add contextual data to an exception, please add a new property instead. On 18 Dec 2016 10:38 a.m., "Wes" <netmo....@gmail.com> wrote: > Good morning nice internals PHPeople, > > I have just written a new RFC. I believe is mostly about cosmetic changes, > as what is being proposed is probably already informally supported by PHP. > > I would like your opinion about it: > https://wiki.php.net/rfc/throwable-code-generalization > > Thank you. >
