Re: type hinting throwing a fatal error
| From: | Steph | Date: | Wed, 24 Aug 2005 14:32:35 +0000 |
| Subject: | Re: type hinting throwing a fatal error | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-18354@lists.php.net to get a copy of this message | ||
Hi Rasmus,
> Steph wrote:
> > If there's the capability to run PHP 6 without Unicode support, surely
> > there's no reason for extensions to lose back compatability when they're
> > updated...?
>
> That's going to be tough. They will definitely lose binary
> compatibility because all sorts of internal structures are changing
> which a runtime switch can't do anything about. We may be able to keep
> compatibility at the source level, but having extensions that fall over
> when you turn on unicode semantics would be a real pain. It might be a
> feature to break them and have a nice FAQ on what needs to be done to
> upgrade the extension to support Unicode.
Ouf - you're effectively saying that Unicode support will need to be enabled
via INI directives on a per-extension basis? Or that there will need to be
two versions of every PHP extension?
> Not that I agree with Derick on changing the meaning of E_ERROR.
:)
- Steph