Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37701
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.171 as permitted sender)
Message-ID: <004f01c8b8ee$9f8f1220$4001a8c0@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@php.net>
Cc: "internals" <internals@lists.php.net>
References: <01b101c8b5c2$66718e20$4001a8c0@foxbox> <1210779138.2986.2.camel@goldfinger>
Date: Sun, 18 May 2008 14:53:55 +0100
Organization: Zend Technologies
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="UTF-8";
	reply-type=original
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Re: unicode.semantics ad infinitum
From: steph@zend.com ("Steph Fox")

Hi all,

> On Wed, 2008-05-14 at 13:59 +0100, "Steph Fox" wrote:
>> I wrote a macro to allow us to use the same code for the extension in 
>> both
>> branches, but it occurs to me that the zstr union definition might change 
>> or
>> even disappear when PHP 6 becomes Unicode-only. Is that likely? I don't
>> know. So keeping it all together is total guesswork at present.
>
> In general: No. We still need both string types at most places, the
> effect of the u.s setting is the default type for strings in the engine.
> Most other functions still need to work with both kinds of string as
> parameter and such. (strlen(b"äöü") vs. atrlen(u"äöü"))

Thanks for that Johannes, done. Next question: should we gear our tests to 
unicode.semantics=off (thereby making us look good on current gcov) or 
unicode.semantics=on (thereby saving extra work in the not-so-distant 
future)?

I've found a couple of minor things that could prevent phars created under 
5_3 from running under 6 with unicode on. They're easily fixable in 5_3, but 
I have to say that optimizing for unicode=off wouldn't have uncovered these.

Another question - when the unicode.semantics switch goes (and please, 
please make it soon someone), the PHP 5 test suite script works fine as-is 
with PHP 6. The one currently in HEAD is probably a bit too clever, trying 
to accommodate both scenarios and failing - unicode=on can't be tested at 
present with that script. So can we revert to the run-tests.php from 5_3 
branch please?

Thanks,

- Steph




>
> johannes
>
>
>
>
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>