Re: php5 beta
| From: | George Schlossnagle | Date: | Fri, 20 Jun 2003 14:11:05 +0000 |
| Subject: | Re: php5 beta | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-2460@lists.php.net to get a copy of this message | ||
On Friday, June 20, 2003, at 10:04 AM, l0t3k wrote:
"Zeev Suraski" <zeev@zend.com> wrote in message news:5.1.0.14.2.20030620024310.06189538@localhost...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. -- George Schlossnagle -- Principal Consultant -- OmniTI Computer Consulting, Inc. -- +1.410.872.4910 x202 -- 1024D/1100A5A0 1370 F70A 9365 96C9 2F5E 56C2 B2B9 262F 1100 A5A0All in all, I would definitely not see errors-as-exceptions as a pre-requisite for the beta. It's not an issue to be dealt with lightly, and we probably won't have time to finalize it in the next few days thatwehave left.fair enough. but in the absence of that solution, the one thing i would greatly appreciate is a modification to zend_parse_parameters (a new parameter ?) to either : 1.) return the text of error messages without raising a warning itself. that way i can raise an IllegalArgumentException or somesuch myself 2.) create and raise an IllegalArgumentException (or just Exception) of its own. right now my code is written assuming something like the second would happen (with the new parameter). so barring that, im in the position of either