Jon Parise wrote: > The convention(*) for these kinds of things is generally to return > 'true' when you've handled the message/event and want to discontinue > further processing. Returning 'false' indicates that you haven't > handled the event.
You are right. That's how it should be done. >> It's backwards compatible with previous functionality, i.e. if you don't >> return anything, the default handler does not get invoked. > > This argument may overrule my preference, of course. Since error_handler is called from inside PHP engine, there should be no noticable BC problem. Only the case when developer calls his function directly too and does so in if/while/etc might be problem. But I don't think this is showstopper. Anyway, neat feature, please add (after return value inversion). Lenar -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
