On Tue, 2004-03-23 at 22:46, Derick Rethans wrote: > No, we decided on no internal functions throwing exceptions (DOM > excluded).
So regardless of context, tidy should be doing docref errors? That takes away a lot from an internal object standpoint. I thought a much better approach would be to have the error reflect the context -- i.e. procedural calls would return docref errors, while object calls would throw exceptions. Unfortunately, since there is no way to determine from EG() if you are called from an object context or not (based on conversations with Andi), the implementation is rather nasty. I don't think anyone can make a strong argument against method calls throwing exceptions, so isn't there any way this little detail can be fixed so that all of the internal objects can behave consistently wrt errors? John -- -=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=- John Coggeshall http://www.coggeshall.org/ The PHP Developer's Handbook http://www.php-handbook.com/ -=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
