RE: [PHP-DEV] exceptions instead of errors
| From: | Steven Brown | Date: | Tue, 13 May 2003 00:08:45 +0000 |
| Subject: | RE: [PHP-DEV] exceptions instead of errors | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-1458@lists.php.net to get a copy of this message | ||
> -----Original Message-----
> From: Marcus Borger [mailto:marcus.boerger@t-online.de]
> Sent: Monday, May 12, 2003 4:56 PM
> To: Steven Brown
> Cc: 'Theo Spears'; internals@lists.php.net
> Subject: RE: [PHP-DEV] exceptions instead of errors
>
>
> At 01:52 13.05.2003, Steven Brown wrote:
> >Maybe I'm just missing something, but if the decision to throw from a
> >function that previously didn't use exceptions for error
> handling is based
> >on if it's being used while in a try {} block, if you wrap your
> new php file
> >with try {} but also make use of an old library, you've just changed the
> >internal behavior of the library code, making it a BC issue.
>
> SURE, but that's the point: if you're trying to mix old and new
> behaviour then
> you can't expect that everything works as expected. If noone here
> is allowed
> to make any progress then we simply stop all development and are fine and
> have some fun in the sun.
>
> And if BC is everything and you want your old libs then simply
> noone forces
> you to use PHP5.
Why should we have to rewrite all our libraries for php5 just to use them?
That seems rather heavy-handed. What's needed is a way to recognize code
written before PHP threw exceptions on internals so PHP can just simply do
the right thing. The '%' prefix on internals idea was one way of doing
that. I'd much rather a solution along those lines exist than have to
rewrite all my code.