Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30370
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain gravitonic.com from 204.11.219.139 cause and error)
In-Reply-To: <35981.78.61.224.253.1183140683.squirrel@avilys.eik.lt>
References: <1181829227.3478.3.camel@localhost.localdomain> <7d5a202f0706141844l3c75b556hdbecbcd5a43747c9@mail.gmail.com> <4671F184.2020401@lerdorf.com> <6sof73dj69ldpspfc5ukrc58qr9ckbin2b@4ax.com> <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> <7A19D00A-9A46-4854-8C5E-26C8F8FAC4B5@gravitonic.com> <35981.78.61.224.253.1183140683.squirrel@avilys.eik.lt>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-ID: <07FB0A7B-9EE1-4F39-BA34-BC5AE2D03FA5@gravitonic.com>
Cc: internals@lists.php.net
Content-Transfer-Encoding: 7bit
Date: Fri, 29 Jun 2007 11:39:36 -0700
To: Tomas Kuliavas <tokul@users.sourceforge.net>
Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6?
From: andrei@gravitonic.com (Andrei Zmievski)

Yes, unfortunately the end user needs to be aware enough of his  
environment to either control the unicode.semantics flag or choose  
the right server to run it on. Believe me, we've tried making  
unicode.semantics controllable on a per-request basis, and after a  
long and hard debate after partial implementation we realized it  
would make both the code and the applications running on top of it  
very fragile.

-Andrei


On Jun 29, 2007, at 11:11 AM, Tomas Kuliavas wrote:

>> It sounds like your libraries are definitely oriented towards working
>> with binary strings, rather than Unicode strings. So, I am not sure
>> why you have unicode.semantics turned on then. If you turn it off,
>> you will get backwards compatibility with PHP 5. And if you do that,
>> you can still create and work on Unicode strings, programmatically.
>
> I've never asked to turn on unicode.semantics. I've asked to give  
> controls
> of unicode.semantics to scripts (PHP_INI_ALL) or at least give me some
> options to turn it off within a script. I don't control PHP version  
> used
> by end user and there is a theoretical possibility that end user  
> will use
> PHP6 with unicode.semantics=on. So I've tested scripts in
> unicode.semantics=on setup. They broke. Lots of notices, broken
> authentication functions, etc.
>
> I want to make sure that I have enough controls to reduce side  
> effects of
> unicode.semantics=on. Currently I can only ask end user to turn it off
> with php_admin_flag or in php.ini.
>
> -- 
> Tomas
>
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php