Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30705
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.92.169 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:references:x-google-sender-auth;
        b=OkCzT8ujeez0ASGmxrzfSngejOyGg2mtx4E8roWjQQ5SOj452luqdtcdId9h1/pOog3X1UrtdydHWc5ergc83CwLrOCS2kOfe6QP96qm+6uGXxM4cZ6zV6rCFOOFxH9oF+Gl9YT/wKOEoHzXdp92l1TrToZx/HQ7nG3dann/lnA=
Message-ID: <30bd80240707091527w6ad30ca5t6b5e6231591dc7da@mail.gmail.com>
Date: Mon, 9 Jul 2007 18:27:05 -0400
Sender: nicobn@gmail.com
To: "Antony Dovgal" <antony@zend.com>
Cc: "Andrei Zmievski" <andrei@gravitonic.com>, 
	"Stanislav Malyshev" <stas@zend.com>, internals@lists.php.net
In-Reply-To: <4692B1A3.1000808@zend.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_177062_23373493.1184020025387"
References: <1181829227.3478.3.camel@localhost.localdomain>
	 <7d5a202f0707060224oa64dfeaw2c7ee17a735648f9@mail.gmail.com>
	 <alpine.DEB.0.98.0707061132430.22750@kossu.ez.no>
	 <468E1158.2030900@lerdorf.com> <468E13C6.1070109@pooteeweet.org>
	 <468E2009.9000703@zend.com> <468E7180.3020709@zend.com>
	 <468E7256.10905@zend.com>
	 <F28DFECF-737A-4387-8317-17B8D78633F3@gravitonic.com>
	 <4692B1A3.1000808@zend.com>
Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6?
From: nicobn@php.net ("=?ISO-8859-1?Q?Nicolas_B=E9rard-Nault?=")

------=_Part_177062_23373493.1184020025387
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Permit me to give my 2 cents on that and share my small bit of experience
with PHP 6.

First of all, I totally agree with you Antony. I'm currently working on
deploying a big codebase in PHP 6 (for those of you who didn't know, I'm th=
e
GSoC student working on refactoring Jaws for PHP 6) and my head started to
ache when I began understanding all the complications of the unicode
implementation as it is right now. Basically, having that
unicode.semanticsPHP_INI switch just totally kills the fun because I
have to have a working
application if it is ON or OFF. Long story short, this forces me to
explicitly define each string as either binary or unicode, which doesn't
make any "PHP sense". It's actually the first time I'm forced to explicitly
specify a variable type in PHP and I'm not sure I'm the only one who's not
happy about this. I like the unicode support and really appreciate all the
work that's been done on it but I absolutely think it should be implemented
without that headache/pain in the ass switch that'll make transition even
tougher for everyone.

In that case, I can say simplicity is certainly not dumb.

On 7/9/07, Antony Dovgal <antony@zend.com> wrote:
>
> On 10.07.2007 01:48, Andrei Zmievski wrote:
> > And I think that we shouldn't, since it removes a big incentive for
> > people to move to PHP 6.
>
> I don't really see much sense in forcing people to use PHP6 if we accept
> the "PHP5 =3D PHP6 - Unicode" formula.
> They are just different things, period.
>
> > Really, we need to get folks to use Unicode natively as much as
> possible.
>
> Andrei, I personally don't need Unicode at all.
> I know, that may sound weird, but that's true.
>
> > This kind of attitude is
> > precisely why we've had and continue to have such an
> > internationalization mess when it comes to building applications.
>
> What attitude are you talking about here?
>
> I'm trying to be honest with myself in the first place.
> Do _I_ like that horrible IS_STRING/IS_UNICODE mess we have atm? No.
> Do _I_ want to maintain this mess in the future just because of some bad
> design decision in the past? Noway, we had enough of that already.
>
> I would love to have clean and easy PHP6 without all the "compatibility",
> which creates gazillion problems to both users and developers.
> Please notice that I didn't call Unicode useless crap or whatever others
> may think about it,
> I just want PHP6 to be Unicode-only release because it would make my
> personal life much easier
> without complicating others' lives.
>
> --
> Wbr,
> Antony Dovgal
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


--=20
Nicolas B=E9rard-Nault (nicobn@gmail.com)
=C9tudiant D.E.C. Sciences, Lettres & Arts
C=E9gep de Sherbrooke

Homepage: http://nicobn.googlepages.com

------=_Part_177062_23373493.1184020025387--