[Fwd: Re: [PHP-DEV] why we must get rid of unicode.semantics switch ASAP]
| From: | Jeremy Privett | Date: | Mon, 21 Jan 2008 16:12:55 +0000 |
| Subject: | [Fwd: Re: [PHP-DEV] why we must get rid of unicode.semantics switch ASAP] | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-34846@lists.php.net to get a copy of this message | ||
Forgot to CC list again.
Just not my day.
-------- Original Message --------
Subject: Re: [PHP-DEV] why we must get rid of unicode.semantics switch ASAP
Date: Mon, 21 Jan 2008 10:11:32 -0600
From: Jeremy Privett <jeremy@omegavortex.net>
Organization: Omega Vortex Corporation
To: Geoffrey Sneddon <foolistbar@googlemail.com>
References: <4794AE48.20005@daylessday.org> <FF5C8368-297C-4F8A-91DD-EC9EBD1407D3@googlemail.com>
Geoffrey Sneddon wrote:
On 21 Jan 2008, at 14:38, Antony Dovgal wrote:And if I remember correctly, there's an explicit typecast (binary) for binary data now, isn't there? -- Jeremy Privett C.E.O. & C.S.A. Omega Vortex Corporation http://www.omegavortex.net Please note: This message has been sent with information that could be confidential and meant only for the intended recipient. If you are not the intended recipient, please delete all copies and inform us of the error as soon as possible. Thank you for your cooperation. -- Jeremy Privett C.E.O. & C.S.A. Omega Vortex Corporation http://www.omegavortex.net Please note: This message has been sent with information that could be confidential and meant only for the intended recipient. If you are not the intended recipient, please delete all copies and inform us of the error as soon as possible. Thank you for your cooperation.3) 2+ bigger codebase [1] (with lots of duplicates because we have to do same things in native and unicode modes);From the cross-reference I assume you mean PHP's codebase. We still need binary string support — Unicode is only suitable for textual content. Images, for example, are binary data and we still need binary strings for them. Not everything people deal with in PHP is a textual string. He could really be referring to both, honestly. The size of codebases in PHP applications will grow as a result, as developers will have to provide the "compatibility ports" for making their code work with both the switch on and off. Either that, or they just have to support one or the other, but not both. Which results in vendors alienating their userbase because they happen to be on a host or server that has the option set out of their favor for whatever reason.