Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54512
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.170 as permitted sender)
MIME-Version: 1.0
Sender: kalle.php@gmail.com
In-Reply-To: <4E443778.2050603@googlemail.com>
References: <4E443778.2050603@googlemail.com>
Date: Thu, 11 Aug 2011 23:56:35 +0200
Message-ID: <CAJW__o0QO6un5SeBhNqckTxGrSMt_G3QLJR+G7UJrRQQC0SCNQ@mail.gmail.com>
To: sebastian.krebs.berlin@googlemail.com
Cc: PHP internals list <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Multibyte and declate (PHP5.4)
From: kalle@php.net (Kalle Sommer Nielsen)

Hi Sebastian

2011/8/11 Sebastian Krebs <sebastian.krebs.berlin@googlemail.com>:
> Hi,
>
> With PHP5.4 I get this warning
>
> | Warning: declare(encoding=...) ignored because Zend multibyte feature
> | is turned off by settings in [..]
>
> because of
>
> | declare(encoding = 'UTF-8');
>
> An except from the manual [1]
>

In PHP 5.4, the compile time switch was removed and made into an ini
directive, which lives under the name of zend.multibyte = [On|Off].

For the question about declare's availability: No Zend Multibyte
support does not make the engine ignore the construct totally, as we
also got another statement; ticks that can be used in declare aswell.

For the question about why its not enabled by default? Performance,
you don't want to enable multibyte support when most of your code
lives in a single byte char format anyway, some calls are most costly
because you can no longer jump just one byte and have to validate what
kind of character sequence we're at now.


-- 
regards,

Kalle Sommer Nielsen
kalle@php.net