Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37794
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain zend.com does not designate 64.97.136.162 as permitted sender)
Message-ID: <001501c8bbf6$5702cf50$4401a8c0@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: "Andrei Zmievski" <andrei@gravitonic.com>
Cc: "Antony Dovgal" <tony@daylessday.org>,
	<internals@lists.php.net>
References: <7d6e34d80805191240k64cb1ba6k3e8f7a50ddf068c@mail.gmail.com> <4831F27B.7030001@suse.de> <296949B4-D328-49FE-968B-4942B28FE869@pooteeweet.org> <7d6e34d80805191454m69614624v7a05037fa947328e@mail.gmail.com> <698DE66518E7CA45812BD18E807866CE019F60DE@us-ex1.zend.net> <34.64.28995.1BE23384@pb1.pair.com> <02e701c8bab7$19a3dd10$4401a8c0@foxbox> <4833FD5B.2010308@daylessday.org> <003f01c8bb33$81ae5030$4401a8c0@foxbox> <48346ED3.9040505@gravitonic.com>
Date: Thu, 22 May 2008 11:26:44 +0100
Organization: Zend Technologies
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="UTF-8";
	reply-type=response
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Unicode progress [Was: unicode.semantics ad infinitum]
From: steph@zend.com ("Steph Fox")

Hey Andrei,

> UG(unicode) checks are still secondary I think - they don't prevent us 
> from doing tests and moving forward, although cleaning them up would be 
> nice.

Cleaning them up would make it possible to find and fix the bugs we already 
know are there ;) There don't seem to be too many, but when it comes to 
tracking down conversions... bleh...

> pack() should take binary strings only, methinks.

It does - 'UG(ascii_conv)' - but sometimes there's a unicode-to-binary 
conversion warning thrown by that, and then you have to cast the variable to 
a binary empty string to suppress the warning before you assign the pack() 
result to it. (See ext/phar/tests/phar_test.inc.) There are similar issues 
with unpack(), and with fwrite()/fread() and friends when dealing with a 
purely binary string.

What concerns me at this point is that we could and should be telling PHP 
users how to future-proof their code during the move from PHP 4 to PHP 5. If 
we can get a fix on that now and get word out, we'll have made their future 
migration path *much* smoother.

- Steph