Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30365
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.146.183 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=b+xitQGBJJnHTvPbrf83+vdUeLy3TKuquw37pvp+r+dhzl+FyEu6eQHVgWgx33Ya7nzdze5eAXmAJa4GfDPEi6Ctz4saNhyXL4z7pbmzcIdAmGVLetOvMLJpKei2XsFu/PzVQHszxFlgWOX4S/3p0iJ9j7Q3iGuh+iaInRoIVmI=
Message-ID: <fe05d1540706290211v683a4a0bka4c28cc3d1f83bf9@mail.gmail.com>
Date: Fri, 29 Jun 2007 11:11:48 +0200
To: "Tomas Kuliavas" <tokul@users.sourceforge.net>
Cc: internals@lists.php.net
In-Reply-To: <41782.78.61.224.253.1183107677.squirrel@avilys.eik.lt>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <1181829227.3478.3.camel@localhost.localdomain>
	 <4677E7B1.2080305@lerdorf.com>
	 <fe05d1540706190808o1d9305b3td74edd6d1c75c97@mail.gmail.com>
	 <4677F5FB.1070206@lerdorf.com> <4678252F.2050803@sci.fi>
	 <46783212.4020900@lerdorf.com>
	 <34654.216.230.84.67.1183064088.squirrel@www.l-i-e.com>
	 <54557.78.61.224.253.1183098089.squirrel@avilys.eik.lt>
	 <4684BB91.4070507@zend.com>
	 <41782.78.61.224.253.1183107677.squirrel@avilys.eik.lt>
Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6?
From: pierre.php@gmail.com (Pierre)

Hi,

On 6/29/07, Tomas Kuliavas <tokul@users.sourceforge.net> wrote:

> For me it means that I have to maintain wrappers for fwrite,
> base64_encode, ord, crc32 and all other unicode aware functions. Any
> direct PHP string or stream function call can cause compatibility issues
> or notices. Any function working with binary data will need separate
> version for PHP6. Instead of having unicode switches in interpreter
> itself, I'll have to implement them in scripts. Talk about performance
> issues after that.

Use the right mode (and stream mode) for the right task solves this
problem. If it does not, there is a bug and it has to be fixed.

But it is possible to work with binary data in php6 just like it was
in php5. The "only" difference is that we have now a working unicode
support which includes true binary data and true unicode data instead
of the all-in-one storage used in previous versions (5.x and earlier).

It is certainly not perfect (see the recent discussions about
file_put_contents in our bug tracker for example), but we are on the
right track. If you have issues/bugs with the way binary strings are
handle (in stream or any other functions) please report them and we
will do our best to fix them.

But not being able to use the same code with php6 and 5.1 is not a
bug. It is simply not possible. You need two files and the performance
impact is minimum here (same interface, two implementations).

--Pierre