Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72739
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.204 cause and error)
Message-ID: <53074806.6020406@lsces.co.uk>
Date: Fri, 21 Feb 2014 12:35:18 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 SeaMonkey/2.24
MIME-Version: 1.0
To: internals@lists.php.net
References: <5301C7F7.2060203@lsces.co.uk> <53024DC6.502@googlemail.com>
In-Reply-To: <53024DC6.502@googlemail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] my take on PHP 6, part 2
From: lester@lsces.co.uk (Lester Caine)

Crypto Compress wrote:
>
> "C++ Usage" discussion is somewhat of a dependency for "Unicode" as it may add
> some more varieties of "awesome Unicode lib".

I don't see that the two do go together, and I'm with Pierre that introducing 
C++ now would only delay progress. It would however be worth serious 
consideration on a longer timeline? I still see unicode as a stepping stone 
which has already been incorporated into PHP by the back door and now simply 
needs a few loose ends tying up. Making it a major version upgraded is more 
about setting the ground rules for other areas than unicode per say. Formalising 
say UTF-8 usage by introducing a few BC breaks opens the debate where trying to 
simply shoehorn the missing UTF-8 elements into PHP5 may not be so practical?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk