PEAR_Exception changes
| From: | Hans Lellelid | Date: | Fri, 23 Jun 2006 14:25:23 +0000 |
| Subject: | PEAR_Exception changes | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-43091@lists.php.net to get a copy of this message | ||
Hi,
I'd like to propose some changes to PEAR_Exception. Thomas, Bertrand,
and I worked on the original version some time ago, and after a bit of
actual use, I have some proposals for improving the way that it handles
wrapped exceptions. In particular, I like to see all the stack traces
for the exceptions that were re-thrown -- and I imagine that others
would like this feature also.
So, my questions:
1) Where is the best place to send the patches (I don't think I have
commit access to that file directly, and even if I do, I imagine changes
to core functionality need to be audited.)
2) What is the policy for making public/protected API changes to
PEAR_Exception? E.g. my proposal would change one of the methods to
make it static. Does any stable package make intimate use (i.e. extend,
call non-stock Exception methods) of PEAR_Exception? (I use it in
Net_GeoIP, but only to throw -- and also that packge is not marked
stable, since I didn't think PEAR_Exception was considered "stable").
Also, must PEAR_Exception be compatible with PHP 5.0.x (as opposed to
5.1.x)? (I assume yes, but figured I'd ask.)
I will wait for answer to (1) before going into more details.
Thanks,
Hans