Fwd: failure notice
| From: | chagenbu at wso dot williams dot edu | Date: | Fri, 26 May 2000 06:09:55 +0000 |
| Subject: | Fwd: failure notice | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-19475@lists.php.net to get a copy of this message | ||
Can someone let us know when the php-pear list is back online?
-chuck
----- Forwarded message from MAILER-DAEMON@toye.php.net -----
<php-pear@lists.php.net>:
That is not a valid email address.
--- Below this line is a copy of the message.
Quoting Stig Bakken <ssb@fast.no>:
> The details of "an error is a negative integer between -1 and -999" is
> hidden from the user. This was done to make it easier to switch to
> another error reporting mechanism (the way the error codes are checked
> would have to be changed, but it's easier to grep for DB_ in your code
> anyway).
This looks like as good a way as we're going to get with what is currently
allowed by PHP.
> PHP has lots of functions with "mixed" return types. I like your
> suggestion, but I think the created error objects should be returned.
> That is the only way the user can catch and handle the errors.
Here I strongly agree. It seems like if a user wants an error handler function,
it would be easy to take a returned Exception and pass it to the error handler.
But if they don't want an error handler function, it's hard to make a system
that is designed to use an error handler return exceptions.
We can even include an example Pear_Error_Handler class that does reasonable
things with any exception passed to it. But I don't want to be forced to use it.
So, where are things with this? Ulf, you mentioned that your system took about
200 lines of code - does that mean you have code that you could let us see? I'd
be interested in getting this rolling a little bit more.
... and while we're on PEAR, two more questions: Ulf, how is phpdoc coming? And
Stig, did you catch any of the javadoc debate, and if so, what is your opinion
on the inline docs in PEAR?
-chuck
----- End forwarded message -----