OK... internals-newb question. Doesn't backporting everything from 6.x to 5.x
except Unicode automatically undermine PHP 6 adoption? If PHP 5.5 ends up
being practically identical to PHP 6 unicode=off because everything has been
backported... what's the incentive for PHP 6 unicode=off to even exist?
Except of course for very subtle differences that didn't get backported so
5.5 is *almost* PHP 6 unicode=off, so no one even deals with PHP 6
unicode=off except for those projects that actively try to run on everything
they can for mass-market compatibility.
Don't get me wrong, I'd love to be able to use namespaces earlier. I'm
confused as to what the long-term advantage is here.
On Monday 23 July 2007, Jani Taskinen wrote:
> Exactly, it will go to 5.3 of course.
>
> --Jani
>
> On Mon, 2007-07-23 at 13:06 +0400, Dmitry Stogov wrote:
> > There is no way to put this patch into 5.2.
> >
> > Dmitry.
> >
> > > -----Original Message-----
> > > From: Timm Friebe [mailto:thekid@thekid.de]
> > > Sent: Saturday, July 21, 2007 1:58 PM
> > > To: PHPdev
> > > Subject: [PHP-DEV] Namespaces patch backport
> > >
> > >
> > > Hi,
> > > I've backported the namespaces patch to current CVS HEAD. Here it is:
> > >
> > > http://sitten-polizei.de/php/php5-namespaces.diff
> > >
> > > I've tested it with the .phpt-tests Dmitry provided. Enjoy:)
> > >
> > > - Timm
> > >
> > > --
> > > PHP Internals - PHP Runtime Development Mailing List
> > > To unsubscribe, visit: http://www.php.net/unsub.php
--
Larry Garfield AIM: LOLG42
larry@garfieldtech.com ICQ: 6817012
"If nature has made any one thing less susceptible than all others of
exclusive property, it is the action of the thinking power called an idea,
which an individual may exclusively possess as long as he keeps it to
himself; but the moment it is divulged, it forces itself into the possession
of every one, and the receiver cannot dispossess himself of it." -- Thomas
Jefferson
