Re: php5 beta
| From: | l0t3k | Date: | Fri, 20 Jun 2003 14:56:01 +0000 |
| Subject: | Re: php5 beta | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-2463@lists.php.net to get a copy of this message | ||
"George Schlossnagle" <george@omniti.com> wrote in message
news:07E7ACBF-A329-11D7-AD2E-000393B2B3C0@omniti.com...
>
> On Friday, June 20, 2003, at 10:04 AM, l0t3k wrote:
> Why don't use just throw an exception yourself in your extension code?
> I'm for errors as exceptions (obviously), but that is only necessary
> for legacy code. In your own new code, raise an exception if you feel
> like it.
my problem is that its double work. IOW, zend_parse_parameters has already
done a good job of parsing and figuring out what went wrong for what reason.
i'd like to be able to use the error message generated by z_p_p rather than
having to figure things out myself. id also like to suppress its generation
of an error, since it would be redundant in the face of the exception.
i've actually considered creating a parallel zend_parse_parameters which has
the required semantics. i'd like to hear other people's takes first, though.
l0t3k