Re: [Fwd: Re: [PEAR-DEV] Re: [ANNOUNCEMENT] HTML_CSS-1.0.0RC1 (beta)Released.]

Lukas Smith wrote:

[1] http://cvs.php.net/pear/HTML_CSS/docs/errorHandlerGuide.txt [2] http://cvs.php.net/co.php/pear/HTML_CSS/CSS.php?r=1.43#1386 [3] http://cvs.php.net/co.php/pear/HTML_CSS/CSS.php?r=1.43#1437 [4] http://cvs.php.net/co.php/pear/HTML_CSS/CSS.php?r=1.43#1468 [5] http://cvs.php.net/co.php/pear/HTML_CSS/CSS/Error.php?r=1.2

So essentially your approach is to keep the implementation of raiseError() inside a user defineable callback? That seems straight forward enough to me. I was fearing there would be alot more code involved. I didnt dig much deeper, but I wonder: are there any public methods that get called from the class itself. In that case I wonder how you deal with the fact that people could set some random error handler? Actually I looked a bit deeper and it seems very few internal method calls have any sort of error handling. So I am really not sure if you are getting this external error handling flexibility by essentially eliminating all internal error handling. Furthermore it would be a good idea to offer a static isError() method so that people can check for HTML_CSS specific errors if they want. regards, Lukas