Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30778
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain users.sourceforge.net from 213.197.162.99 cause and error)
Message-ID: <43346.195.22.180.233.1184147948.squirrel@avilys.eik.lt>
In-Reply-To: <200707110015.53800.larry@garfieldtech.com>
References: <1181829227.3478.3.camel@localhost.localdomain>
    <698DE66518E7CA45812BD18E807866CE647A32@us-ex1.zend.net>
    <46942A82.90909@rooftopsolutions.nl>
    <200707110015.53800.larry@garfieldtech.com>
Date: Wed, 11 Jul 2007 12:59:08 +0300 (EEST)
To: internals@lists.php.net
User-Agent: NaSMail/1.2
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
Importance: Normal
Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6?
From: tokul@users.sourceforge.net ("Tomas Kuliavas")

>> > I think the sooner the better as it's valuable information for the dev
>> > team.
>> > It'd probably be a good idea to have a Wiki where we can document
>> issues
>> > that/common use-cases which are encountered.
>> > Maybe we should have a Wiki on one of the php.net servers for such
>> > purposes?
>> > Andi
>>
>> Is anyone aware of a list with a, say top 10 PHP applications?
>>
>> When such a wiki is setup, how would you suggest to write such
>> documents.. At least a generic guide would be good (e.g.: common
>> pitfalls)
>> Should I be documenting the per-project specifics as well?
>>
>> Evert
>
> Top 10 by what metric?  If I had to guess based on market share, I'd say
> (unordered):
>
> Drupal
> Squirrelmail

SquirrelMail

1. remove session_unregister call

2. fix get_magic_quotes_gpc() call

3. Turn off unicode.semantics in webserver configuration or php.ini

SquirrelMail scripts are designed to work with binary strings. Lots of
SquirrelMail functions are not compatible with unicode.semantics=on. Some
calls are not prepared to handle changes in crc32(), base64_encode(),
fputs() and fwrite(). If scripts keep backwards compatibility, they will
need wrappers for most of affected string and stream functions.

Some unicode.semantics=on side effects can be fixed without splitting
functions between PHP5 and PHP6, but unicode.script_encoding can't be set
with ini_set() and must be declared on top of all affected scripts.


-- 
Tomas