Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72719
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.43 as permitted sender)
Message-ID: <5306677A.7070000@gmail.com>
Date: Thu, 20 Feb 2014 21:37:14 +0100
User-Agent: Thunderbird
MIME-Version: 1.0
To: Pierre Joye <pierre.php@gmail.com>
CC: Andrea Faulds <ajf@ajf.me>, PHP internals <internals@lists.php.net>
References: <69AB9D0D-FF9E-42BE-B91C-827F7810B0F6@ajf.me> <CAEZPtU7tUmLyh97_1FLcOnnSTmRO+pACu8_BMaDG13CEt-Dy1A@mail.gmail.com>
In-Reply-To: <CAEZPtU7tUmLyh97_1FLcOnnSTmRO+pACu8_BMaDG13CEt-Dy1A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Simpler Unicode solution for PHP6
From: keisial@gmail.com (=?UTF-8?B?w4FuZ2VsIEdvbnrDoWxleg==?=)

On 20/02/14 17:23, Pierre Joye wrote:
> Hi,
>
> On Feb 20, 2014 11:17 PM, "Andrea Faulds"<ajf@ajf.me>  wrote:
>> Hi,
>>
>> As a simpler to implement approach to Unicode, could we perhaps support
> it just by adding an “is UTF-8” flag to strings internally? Then unmodified
> functions would just see a normal string and handle it like they do any
> other, and modified and new Unicode-aware functions would test for the
> presence of the flag and handle the string appropriately in that case.
>> Thoughts?
> That could be an option during the development phase. However I do not like
> the idea of a flag for the final implementation, it creates more troubles
> from an application point of view.
Optimizing space? The flag could be embedded with the type.

Create a macro for checking if it's of type IS_STRING_RAW or IS_STRING_UTF8,
and replace with it the hundreds of IS_STRING comparisons (it would 
affect many
lines, but not hard).