Ivan Ristic <[EMAIL PROTECTED]> wrote... :
> > > I will start laying out some my thoughts to hopefully get a discussion > > towards working on the complete error reporting logic. I had an > > extensive experience implementing custom errors, so approve or > > disapprove my ideas. > > I like your ideas too, but some of your suggestions need to > be compared to the exception mechanism, to avoid duplicated > effort. You are right. Extension errors, such as the ones returned from database, should be incorporated in a way that you can pass them to the end user. I think with a little bit of logic this is very much doable. For instance, in one of the project I have done it like: "Error 1256: Cannot Connect to Oracle Listener. Oracle reported $ora_error" where you pass as the parameter the actual message Oracle receives. So, in my opinion it is simple do accomplish. > > I have been following the thread about error reporting thing and, I > > think, it is all going off route. > > > While I do agree that the error handling mechanism needs to > be enhanced, none of your suggestions are directly related > to the error handling discussion and the patch. I think > we should finish with the patch discussion first so that > we can later proceed to more complex issues. > Completely agree again. It is why I started the new thread. Throwing this idea on another time can sound rush. Rright now, when our heads are occupied analysing error reporting, this can result being more productive, IMO. And, it is till related anyway. -- Maxim Maletsky [EMAIL PROTECTED] -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
