Naïve. Most core developers will spend their time and energy on PHP 6, and you will quickly see non-Unicode features being added to PHP 6 and not other versions. It's always been like that in PHP's history.
Andi > -----Original Message----- > From: Steph Fox [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 06, 2006 6:36 PM > To: Andi Gutmans; 'Andrei Zmievski'; 'PHP Internals' > Cc: 'Dmitry Stogov' > Subject: Re: [PHP-DEV] RFC: unicode.semantics: runtime or not? > > Can anyone explain to me why it would be such a big problem > to support PHP 6 and PHP 5 alongside one another? With PHP 6 > effectively being a Unicode-supporting version of PHP 5? > > Or am I being weird and naive here? > > - Steph > > > > As Andrei knows, I believe that not allowing to tune this on a per > > virtual host basis, is going to make life very hard for our > users. A > > huge part of our users are hosting providers, or companies running > > multiple applications on the same machine. Probably a > majority do not > > own dedicated boxes. This kind of limitation is going to > not only slow > > down PHP 6 adoption, but I think it may also significantly > impair PHP > > as a hosting friendly solution, and therefore, we could > actually see a > > loss in overall PHP market share. > > > > I suggest to first make the theoreticaly decision that we prefer to > > support this on a per-request if it's feasible. When I say > feasible it > > means with some but minimal pain. If it becomes a disaster > we should > > re-evaluate. > > I'll > > try and spend the next week to try and see what the issues are and > > whether we can resolve them in an acceptable way. > > > > Andi > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
