Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:31119
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.82.238 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=f78p8HV2HMnoXfpPxOJOCP8hkEyxDuV3LWxmxcKwiRLaxdq/zn2BE6knUuGzCKN8lPTblLgvQcl/HBREEE2EP5be3IWMeemq9MEASooe9Yaz8tSM11BvURZWkLN4uN7d8y8xhU8W+nir7Nz12ghvDc1UlUXXQduz4r2cA/mOcUU=
Message-ID: <b5f7bf6c0707191620l6be197bal12e4adef0fd5798a@mail.gmail.com>
Date: Thu, 19 Jul 2007 19:20:53 -0400
Sender: david.coallier@gmail.com
To: scott.mcnaught@synergy8.com
Cc: internals@lists.php.net
In-Reply-To: <-4830671619941995385@unknownmsgid>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <698DE66518E7CA45812BD18E807866CE648191@us-ex1.zend.net>
	 <469C6436.2060009@pooteeweet.org>
	 <698DE66518E7CA45812BD18E807866CE6483DF@us-ex1.zend.net>
	 <469CD717.2070607@pooteeweet.org> <469CE8CE.5080208@zend.com>
	 <alpine.DEB.0.98.0707181006010.10300@kossu.ez.no>
	 <698DE66518E7CA45812BD18E807866CE648722@us-ex1.zend.net>
	 <20A6448D-A497-4D95-AA9E-72D69421BB88@gravitonic.com>
	 <469FE9F6.7050406@zend.com> <-4830671619941995385@unknownmsgid>
Subject: Re: [PHP-DEV] POSIX regex
From: davidc@php.net ("David Coallier")

On 7/19/07, scott.mcnaught@synergy8.com <scott.mcnaught@synergy8.com> wrote:
> I don't like the idea of having a "u" prefix for Unicode strings.  It may
> improve performance, and give you some level of fine grain control, but...
>
> - It breaks your "keep php simple" policy by introducing a lot of new
> functions (ugly).
> - I (plus a lot of others) have an existing php5 application which I wish to
> eventually use with Unicode, and like others, I don't want to spend time
> refactoring.
> - It will also introduce bugs when programmers accidentally forget to add
> the "u" prefix when working with unicode.
>
> If you always want to produce Unicode, I think its best to always use a cast
> or a conversion function.
>
> Eg
>
> $str = (unicode)(strtoupper($str));
> Or
> $str = unicode_val(strtoupper($str));
>
> My 2c :)
>

Yeah I also like that casting better than the "u"

$0.02 :P

>
>
>
> -----Original Message-----
> From: Stanislav Malyshev [mailto:stas@zend.com]
> Sent: Friday, 20 July 2007 8:47 AM
> To: Andrei Zmievski
> Cc: Andi Gutmans; Derick Rethans; Lukas Kahwe Smith; Ilia Alshanetsky;
> jani.taskinen@iki.fi; internals@lists.php.net
> Subject: Re: [PHP-DEV] POSIX regex
>
> > Python did go down that road, but take a look at Python 3000 effort and
> > you will see that what they are trying to do is exactly what we have:
> > native Unicode strings, without prefixes.
>
> Maybe still having u"" - that always produce unicode, regardless of
> semantics - could be helpful...
>
> --
> Stanislav Malyshev, Zend Software Architect
> stas@zend.com   http://www.zend.com/
> (408)253-8829   MSN: stas@zend.com
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


-- 
David Coallier,
Founder & Software Architect,
Agora Production (http://agoraproduction.com)
51.42.06.70.18