Re: Re: [PHP-DEV] 6.0 And Moving Forward
| From: | Brandon Wamboldt | Date: | Tue, 17 Jul 2012 12:59:25 +0000 |
| Subject: | Re: Re: [PHP-DEV] 6.0 And Moving Forward | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-61347@lists.php.net to get a copy of this message | ||
I like this idea a lot. I use PHP at work, and run everything on dedicated
servers so I'd definitely prefer to run a pure PHP6 setup. Hosting
providers on the other hand can over PHP5 support via an extension.
+1
On Tue, Jul 17, 2012 at 9:51 AM, Leigh <leight@gmail.com> wrote:
> > Basically, the current function library is moved to the legacy
> > namespace. The default setting is import the functions of the legacy
> > namespace into the root namespace for BC. But with that setting
> > turned off all the existing functions go away to be replaced with a
> > designed API, instead of a grown one, correcting the mistakes that
> > have accumulated over the years.
>
> Is there any reason why this cannot / should not be implemented as a
> PHP 5 compatibility extension?
>
> I think those who never want to use it (PHP 6 purists) shouldn't have
> to have their binaries bloated by legacy code. It would also mean that
> the legacy implementation can be developed away from the new core, and
> not have any (negative) influence on it.
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
*Brandon Wamboldt*
Programmer / Web Developer
StackOverflow Careers
Profile<http://careers.stackoverflow.com/brandonwamboldt>-
GitHub
Profile <https://github.com/brandonwamboldt>
-
LinkedIn<https://github.com/brandonwamboldt>
-
My Blog <http://brandonwamboldt.ca/>