Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30253
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.235.23.12 as permitted sender)
To: rasmus@lerdorf.com (Rasmus Lerdorf)
Cc: internals@lists.php.net
Date: Tue, 19 Jun 2007 16:39:45 +0200
Message-ID: <m5qf73pn8bqlul8omcugo04b5po9a9cq7g@4ax.com>
References: <1181829227.3478.3.camel@localhost.localdomain> <7d5a202f0706141844l3c75b556hdbecbcd5a43747c9@mail.gmail.com> <4671F184.2020401@lerdorf.com> <6sof73dj69ldpspfc5ukrc58qr9ckbin2b@4ax.com> <4677E7B1.2080305@lerdorf.com>
In-Reply-To: <4677E7B1.2080305@lerdorf.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6?
From: penguin@php.net (Peter Brodersen)

On Tue, 19 Jun 2007 07:26:57 -0700, in php.internals
rasmus@lerdorf.com (Rasmus Lerdorf) wrote:

>> I think we were really close to get out of the
>> if(get_magic_quotes_gpc()) "requirement" but now it has been replaced
>> with a new one. Even if a developer would write (portable) PHP 6 only
>> code.
>
>But this is no different from writing code that will work on both PHP 5
>and PHP 6.  The only difference is that instead of checking for PHP 5
>you will be checking for Unicode.

Yeah, but that's pretty much the problem :)

If I want to create code that has to work under different versions of
PHP then it's a no-brainer that I have to check for different settings
(and maybe even create userland functions to emulate native functions
in later versions of PHP). The more BC the code has to maintain the
more settings does one have to check for.

But if I want to code to one specific version of PHP it bothers me
that I even here has to take in consideration that PHP still comes in
different flavors, even under one version.

If the unicode setting would be on for most of the installments I
might just create assumptions on this setting - pretty much the same
way that I have dared to assume that magic_quotes_runtime and
magic_quotes_sybase is off (as I have never encountered them on in
generel setups such as webhosting companies).

But my fear is that exactly the webhosting companies would end up with
different settings and might even have to create two products for
their customer: "Do you want the PHP 6 with unicode setting on or
off?".

I'm just worried that PHP 6 is the new NULL: PHP6 !=3D PHP6 :-)

--=20
- Peter Brodersen