Hello Markus, Sunday, November 30, 2003, 10:59:50 PM, you wrote:
> Hi, > On Sat, Nov 29, 2003 at 06:09:36PM +0100, Marcus Boerger wrote : >> this works now. > Thanks. Sorry for the order of reply of the mails, my spam filer > catches this one and I only discovered it yet. >> > Besides the segfaults above, is there a chance we have a nicer HTML >> > formatting for reported Exceptions (while still strip those HTML >> > tags from it for logging)? > Can you advise in this issue too? > The thing is, the stack trace is alright and looks good, but not in > HTML since the line breaks are ordinary ones; there's not HTML > formatting for them, so the line break is not visible in the HTML > output. > If I derive my own exception and override __toString() I can call > nl2br(); but then I've the HTML output in the error_log too. > Seems like an chicken and egg problem. Another solution is to modify > error_prepend/append to encapuslate the error output in a pre block. There you go. > Besides this possible, would it be feasable to handle this issue > right away in PHP for HTML and error log output? Maybe it's not > possible anyway. Hm. I don't think this makes sense but maybe we *could* try to establish a callback into main to display uncaught exceptions. But this must wait until after 5 release i think. -- Best regards, Marcus mailto:[EMAIL PROTECTED] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
