Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47300
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.219 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type;
        b=VDUNd/ptxuNwmW0Mpc7n+rSFeSCGyhRCETtwEg0QIslP+awAFPrftIgJxjGcNCfbIy
         bcKVTKUn4/Hn75U6JjoW/ejWuhtNbxYSTonhHoRlHUEB9OVt8XHZ1/htZ9u7Fyb83coC
         fLNPBAt9ZpGFcSdruGWeev5szCfBhd8Jvg+m0=
MIME-Version: 1.0
In-Reply-To: <4B9F4196.9030404@lsces.co.uk>
References: <4B9C9007.1080802@lsces.co.uk> <4B9EC3B2.7070901@zend.com> 
	<4B9F4196.9030404@lsces.co.uk>
Date: Tue, 16 Mar 2010 11:48:00 +0000
Message-ID: <99cf22521003160448k5028ae61y70e1e61428d13280@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Where are we ACTUALLY on Unicode?
From: dreamcat4@gmail.com (dreamcat four)

On Tue, Mar 16, 2010 at 8:30 AM, Lester Caine <lester@lsces.co.uk> wrote:
> '3' is not a very processor friendly number, so working with 4 even though
> wasteful on memory, does make perfect sense. How long is it since we had a
> 640k limit on working memory? SERVERS should have a good amount of memory
> for caching information anyway. SO is UTF-16 the right approach for
> processing wide strings? It needs special code to handle everything wider
> than 16 bits, but at what gain really? If all core functionality is handled
> as 32 bit characters is there that much of an overhead over the additional
> processing to get around strings of dissimilar sizes in UTF-16 ?

Just to re-enforce some of Lester's points above here.

4-byte per character is never slower that 2-bytes per character... its
faster if anything. Bear in mind that 4-byte has been the defacto size
for all modern cpu registers / 32-bit microarchitectures since....
like... Forever. Give a c compiler 4bytes of data... it'll say: thank
you very much, and more of the same please! It keeps em happy ;)

Sure UTF-16 can make sense. But only if your external representations
are also in UTF-16. So whats the default Unicode settings for MYSQL,
POSTGRE, etc? Well, are they always set to UTF-8, or UTF-16?

Just do the same as them.